Hi,
I only use XXE for french translation.
There is some configuration for XXE like:
<cfg:preserveSpace xmlns=""
elements="address funcsynopsisinfo classsynopsisinfo
literallayout programlisting screen synopsis" />
or
<cfg:saveOptions cdataSectionElements="programlisting" />
The first one to maintain space in programlisting. And the second to use
CDATA in programlisting instead of <.
Mickael.
Bradley Holt a écrit :
Simon,
That's exactly what I was wondering - if XXE played well with the
current ZF doc setup (apparently it doesn't). I've only used it for
documentation that I created (but I have kept a close eye on the XML
output and have been happy with what I've seen). For non-programmers
(or people who don't want to hand-edit XML) its a really nice tool.
We've been using it for non-programmers to generate XHTML content
since it focuses on structure (WYSIWYM
<http://en.wikipedia.org/wiki/WYSIWYM>), not presentation (WYSIWYG).
Too bad it doesn't play well with the ZF docs :-)
Thanks,
Bradley
On Thu, Jul 31, 2008 at 5:27 PM, Simon Mundy <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Brad,
FWIW I began using XMLMind to create and update entries in the ZF
documentation.
It had a tendency to mash existing code examples (e.g. converting
all < to < and removing CDATA instructions) and muck around
with every single line re: whitespace. In turn this meant the
documentation guys had real trouble determining what had been
changed, as the change logs showed that every line was updated,
thus drawing out the process.
As an editor it's brilliant - I use it a lot for other projects.
Maybe the paid-for version allows more fine-grained control over
the output, but for now I'll stick with hand-coding when it comes
to ZF updates.
Cheers
Matt,
Sorry about continuing an OT discussion, but I'm curious what you
mean when you say the XML from XMLmind XML Editor (XXE) wasn't
"good enough?" My experience with XXE has been that the XML was
perfectly valid, well formatted in respect to whitespace, and met
the DocBook specs. I find it surprising that it's quicker for you
to copy-and-paste from Microsoft Word than it is to just use a
structured content editing tool like XXE from the beginning. In
my understanding, the whole point of structured content is that
you're considering both content and structure at the same time.
On Thu, Jul 31, 2008 at 2:39 PM, Matthew Ratzloff
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Microsoft Word, and then translated into DocBook by hand.
This is the quickest way for me that I've found. The first
part I worry about the content. Only then do I worry about
the semantics and formatting.
I tried using XMLmind's editor once for client documentation
at work. I dumped it. The XML it produces just wasn't good
enough.
-Matt
On Thu, Jul 31, 2008 at 6:41 AM, Keith Pope
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Hey guys,
Do you use a docbook editor for writing the zf docs? If
so whats a good editor to use?
Thx
Keith Pope
--
allpay.net <http://allpay.net> Limited, Fortis et Fides,
Whitestone Business Park, Whitestone, Hereford, HR1 3SE.
Registered in England No. 02933191. UK VAT Reg. No. 666
9148 88.
Telephone: 0870 243 3434, Fax: 0870 243 6041.
Website: www.allpay.net Email: [EMAIL PROTECTED]
This email, and any files transmitted with it, is
confidential and intended solely for the use of the
individual or entity to whom it is addressed. If you have
received this email in error please notify the allpay.net
<http://allpay.net> Information Security Manager at the
number above.
--
Bradley Holt
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
--
Simon Mundy | Director | PEPTOLAB
""" " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" "
202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000
Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3
9654 4124
http://www.peptolab.com
--
Bradley Holt
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
