From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/70010 Path: news.gmane.org!not-for-mail From: John Haltiwanger Newsgroups: gmane.comp.tex.context Subject: Re: Edit a ConTeXt generated document with Adobe Acrobat Professional Date: Thu, 14 Jul 2011 17:15:34 -0700 Message-ID: References: <4E1EFF0C.50401@wxs.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1470425156==" X-Trace: dough.gmane.org 1310688963 29767 80.91.229.12 (15 Jul 2011 00:16:03 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 15 Jul 2011 00:16:03 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Fri Jul 15 02:15:59 2011 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QhW4V-0007YQ-FQ for gctc-ntg-context-518@m.gmane.org; Fri, 15 Jul 2011 02:15:59 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id B17B8CAE3F; Fri, 15 Jul 2011 02:15:58 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id O4JUu5L-luJf; Fri, 15 Jul 2011 02:15:52 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id A19D7CAE3A; Fri, 15 Jul 2011 02:15:52 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 9038DCAE3A for ; Fri, 15 Jul 2011 02:15:50 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ki-oea2IVwXr for ; Fri, 15 Jul 2011 02:15:36 +0200 (CEST) Original-Received: from filter4-nij.mf.surf.net (filter4-nij.mf.surf.net [195.169.124.155]) by balder.ntg.nl (Postfix) with ESMTP id 30881CAC8D for ; Fri, 15 Jul 2011 02:15:36 +0200 (CEST) Original-Received: from mail-fx0-f42.google.com (mail-fx0-f42.google.com [209.85.161.42]) by filter4-nij.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p6F0FY9x021313 for ; Fri, 15 Jul 2011 02:15:35 +0200 Original-Received: by fxe23 with SMTP id 23so1671137fxe.15 for ; Thu, 14 Jul 2011 17:15:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Y0uF7xD416KlA0bSTGK6vhKlzKPhZnsjlbv42oHo4fc=; b=pmErR5RkhhP1z4MXLyQFCkEouQrz20HcVURT5BQwxFmEaCHryzj6YfD9n9un9iZ5c5 cxBhce9Y/ldzYsky3x2OXHvr0uaUW6PNT2rXmPvXehwI5Z1jnZv78cupFnzEXCtrwTAC UvE842HACzuL6i7ZoMOU6gerFdRsR6fEHAecQ= Original-Received: by 10.223.68.22 with SMTP id t22mr4306128fai.145.1310688934577; Thu, 14 Jul 2011 17:15:34 -0700 (PDT) Original-Received: by 10.223.111.13 with HTTP; Thu, 14 Jul 2011 17:15:34 -0700 (PDT) In-Reply-To: X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN) X-CanIt-Geo: ip=209.85.161.42; country=US; region=CA; city=Mountain View; postalcode=94043; latitude=37.4192; longitude=-122.0574; metrocode=807; areacode=650; http://maps.google.com/maps?q=37.4192,-122.0574&z=6 X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 04F80fyvC - a879593719c1 - 20110715 X-Scanned-By: CanIt (www . roaringpenguin . com) on 195.169.124.155 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:70010 Archived-At: --===============1470425156== Content-Type: multipart/alternative; boundary=0015174c13265b456004a8108c9c --0015174c13265b456004a8108c9c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Jul 14, 2011 at 3:18 PM, Martin Schr=F6der wrot= e: > 2011/7/14 John Haltiwanger : > > Pandoc, so I'm not familiar with Context's xhtml capacities. > > MkIV can create XML. :-) > That is something I have heard much more than I have seen. If it can so easily do so, could a wizard please intervene and provide a recipe for producing XHTML from standard Context input?[^1] I have no doubt it can, but documentation of this relative necessity in this age of multi-output publishing is suboptimal.[^2] I swear that this information will go down throughout the ages as a conduit for better typography (and th= e wiki page dedicated to this process will become a keystone of expanded possibility in the future). Cecil, I don't think its fair to constrain yourself from ever using Context again. What does 'competely independent' mean? If you have been asked to hand over layout decisions, the best is to reproduce your document in XHTML, copy it into a word processor, and let them proceed with their own desing in their proprietary WYSIWYG software. Even if they just want to make textual changes, this is probably still be your best bet. You can then relatively easily convert them back to Context (a matter of re-mapping text into Context). There is a plan I have to produce an easier-for-point-and-clickers interface to collaborate on high quality Context based layouts, but the time hasn't appeared to materialize it yet. If you search through the archives for 'pandoc' you will see that many of u= s have chosen to abstract ourselves from direct dependence on Context for our document 'coding'. There is a tangible flexibility provided by writing in a visually semantic preformat like Markdown. It helps during the editing stages because it is easy to generate other formats that people are more familiar with (OpenOffice can be converted to Word---then it is a matter of 'backporting' changes to the Context source). If they weren't clear about planning to take on this design responsibility--which they should have long before the deadline--than I fee= l it is the fault of the editors and not the fault of Context. Under such conditions I would have written text for these people in something they understand, like an word processor document (LibreOffice can save as MS Wor= d easily enough). Sorry to hear you are having trouble with this. I know what it is like to face the edge of a deadline. PS. For what it is worth, I do not think it would be _too_ hard to create a Context to Markdown translator.[^3] Since the backend supports XML, it should be able to map to a different semantic markup without much trouble.. right? [^1]: No CSS necessary, just classes and/or ids mapped to environment names= . Apologies to anyone who has answered this question before: just point me towards where the answer is and I will make sure it finds its way to a prominent place on the wiki. [^2]: I understand that there is a description at the wiki, but it is many years old, maybe older than LuaTeX (the history says it is from 2007). Something fresher is in order I think. > > Best > Martin > > _________________________________________________________________________= __________ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > > _________________________________________________________________________= __________ > --0015174c13265b456004a8108c9c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Jul 14, 2011 at 3:18 PM, Martin Schr= =F6der <martin@oneiros.de> wrote:
2011/7/14 John Haltiwanger <john.haltiwanger@gmail.com>:
> Pandoc, so I'm not familiar with Context's xhtml capaciti= es.

MkIV can create XML. :-)

That is = something I have heard much more than I have seen.

If it can so easi= ly do so, could a wizard please intervene and provide a recipe for producin= g XHTML from standard Context input?[^1] I have no doubt it can, but docume= ntation of this relative necessity in this age of multi-output publishing i= s suboptimal.[^2] I swear that this information will go down throughout the= ages as a conduit for better typography (and the wiki page dedicated to th= is process will become a keystone of expanded possibility in the future).
Cecil, I don't think its fair to constrain yourself from ever using= Context again. What does 'competely independent' mean?

If you have been asked to hand over layout decisions, the best is to reprod= uce your document in XHTML, copy it into a word processor, and let them pro= ceed with their own desing in their proprietary WYSIWYG software.

Even if they just want to make textual changes, this is probably still be y= our best bet. You can then relatively easily convert them back to Context (= a matter of re-mapping text into Context). There is a plan I have to produc= e an easier-for-point-and-clickers interface to collaborate on high quality= Context based layouts, but the time hasn't appeared to materialize it = yet.=A0

If you search through the archives for 'pandoc'= you will see that many of us have chosen to abstract ourselves from direct= dependence on Context for our document 'coding'. There is a tangib= le flexibility provided by writing in a visually semantic preformat like Ma= rkdown. It helps during the editing stages because it is easy to generate o= ther formats that people are more familiar with (OpenOffice can be converte= d to Word---then it is a matter of 'backporting' changes to the Con= text source).

If they weren't clear about planning to take on thi= s design responsibility--which they should have long before the deadline--t= han I feel it is the fault of the editors and not the fault of Context. Und= er such conditions I would have written text for these people in something = they understand, like an word processor document (LibreOffice can save as M= S Word easily enough).

Sorry to hear you are having trouble with this. I know = what it is like to face the edge of a deadline.

PS= .=A0For what it is worth, I do not think it would be _too_ hard to create a= Context to Markdown translator.[^3] Since the backend supports XML, it sho= uld be able to map to a different semantic markup without much trouble.. ri= ght?

[^1]: No CSS necessary, just classes and/or ids mapped = to environment names. Apologies to anyone who has answered this question be= fore: just point me towards where the answer is and I will make sure it fin= ds its way to a prominent place on the wiki.

[^2]: I understand that there is a description at the wiki, but it is m= any years old, maybe older than LuaTeX (the history says it is from 2007). = Something fresher is in order I think.
=A0

Best
=A0 Martin
_______________________________________________= ____________________________________
If your question is of interest to others as well, please add an entry to t= he Wiki!

maillist : ntg-cont= ext@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage =A0: http://= www.pragma-ade.nl / http://tex.aanhet.net
archive =A0: http://foundry.supelec.fr/projects/contextrev/
wiki =A0 =A0 : http:= //contextgarden.net
___________________________________________________________________________= ________

--0015174c13265b456004a8108c9c-- --===============1470425156== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________ --===============1470425156==--