From: Cecil Westerhof <cldwesterhof@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Edit a ConTeXt generated document with Adobe Acrobat Professional
Date: Fri, 15 Jul 2011 10:17:21 +0200 [thread overview]
Message-ID: <CAG-LmmDRigo7T=ScHMuC4p2PCxpgGNDGbaKaupSBow=nKAUs1g@mail.gmail.com> (raw)
In-Reply-To: <CANenyVPzfLmxjgSrDWE21zgh4vbDB1S484L2CMQP+rkZOa4v8g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2933 bytes --]
2011/7/15 John Haltiwanger <john.haltiwanger@gmail.com>
> Cecil, I don't think its fair to constrain yourself from ever using Context
> again.
That was not what I mend. When making my own stuff where I do not have the
need off interoperability I will keep using it. But in other case I should
evaluate the situation correctly. Between a rock an a hard place is not a
nice position. ;-}
> What does 'competely independent' mean?
>
Properly that anybody that knows how to write a document in Microsoft Office
can change the document. So standard software, with a low learning curve. I
had some problems getting them to accept to use Adobe. And now that turns
out to be not a real option. Learning all the time as Benny Hill said.
> 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.
>
No the problem is not the layout. They are satisfied with that. They just do
not want to be dependent on our company.
> 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).
>
That sounds like a good plan. Converting back is properly not necessary. But
it would not hurt if it is possible.
> 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.
>
Sounds good. If I could be of help …
> 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 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).
>
I'll do that.
> If they weren't clear about planning to take on this design
> responsibility--which they should have long before the deadline--than I feel
> 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 Word
> easily enough).
>
That is what I mend that in hindsight I should not have used ConTeXt. ;-}
> Sorry to hear you are having trouble with this. I know what it is like to
> face the edge of a deadline.
>
I'll survive, I always did. :-D
I have to thank this list for the help and support.
--
Cecil Westerhof
[-- Attachment #1.2: Type: text/html, Size: 4534 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-07-15 8:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 14:04 Cecil Westerhof
2011-07-14 14:11 ` luigi scarso
2011-07-14 14:29 ` Cecil Westerhof
2011-07-14 14:37 ` Hans Hagen
2011-07-14 15:18 ` Cecil Westerhof
2011-07-14 15:26 ` Cecil Westerhof
2011-07-14 15:27 ` Martin Schröder
2011-07-14 16:01 ` Cecil Westerhof
2011-07-14 16:13 ` Mojca Miklavec
2011-07-14 16:47 ` Cecil Westerhof
2011-07-14 16:13 ` John Haltiwanger
2011-07-14 16:51 ` Cecil Westerhof
2011-07-14 16:57 ` John Haltiwanger
2011-07-14 17:17 ` Cecil Westerhof
2011-07-14 17:30 ` Mojca Miklavec
2011-07-14 19:51 ` Cecil Westerhof
2011-07-14 22:18 ` Martin Schröder
2011-07-15 0:15 ` John Haltiwanger
2011-07-15 6:29 ` Taco Hoekwater
2011-07-15 8:35 ` Cecil Westerhof
2011-07-15 8:44 ` Hans Hagen
2011-07-15 8:17 ` Cecil Westerhof [this message]
2011-07-15 8:47 ` Andreas Schneider
2011-07-15 8:58 ` Cecil Westerhof
2011-07-15 9:09 ` luigi scarso
2011-07-18 18:10 ` ConTeXt to Markdown (was Edit a ConTeXt generated document with Adobe Acrobat Professional) Aditya Mahajan
2011-07-19 10:25 ` Cecil Westerhof
2011-07-19 10:27 ` Martin Schröder
2011-07-19 10:41 ` John Haltiwanger
2011-07-19 10:46 ` luigi scarso
2011-07-19 10:51 ` Cecil Westerhof
2011-07-19 12:37 ` Hans Hagen
2011-07-19 12:45 ` luigi scarso
2011-07-19 12:52 ` Khaled Hosny
2011-07-14 17:18 ` Edit a ConTeXt generated document with Adobe Acrobat Professional Peter Münster
2011-07-14 19:42 ` Cecil Westerhof
2011-07-14 14:37 ` luigi scarso
2011-07-14 15:09 ` Cecil Westerhof
2011-07-14 15:19 ` luigi scarso
2011-07-14 15:20 ` Khaled Hosny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG-LmmDRigo7T=ScHMuC4p2PCxpgGNDGbaKaupSBow=nKAUs1g@mail.gmail.com' \
--to=cldwesterhof@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).