Frank Sundermeyer held a talk about DAPS
- our DocBook Authoring and Publishing Suite --
at LinuxTag2012 last week in Berlin.
Here is the Video:
http://blip.tv/opensuse/linuxtag2012-docbook-publishing-and-authoring-made-…
See the project page at http://daps.sourceforge.net/
cheers,
JW-
--
o \ Juergen Weigert paint it green! __/ _=======.=======_
<V> | jw(a)suse.de back to ascii! __/ _---|____________\/
\ | 0911 74053-508 say #263A!__/ (____/ /\
(/) | _____________________________/ _/ \_ vim:set sw=2 wm=8
SUSE LINUX Products GmbH, GF: Jeff Hawn, J.Guild, F.Imendoerffer, HRB 16746
(AG Nuernberg), Maxfeldstrasse 5, 90409 Nuernberg, Germany
SuSE. Supporting Linux since 1992. ☺
--
To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org
Hi,
I am trying to update the french translation of openSUSE manuals but I have some problems. It seems to come from xml2po which does not handle right productnamereg and productname tags:
<!ENTITY productname '<phrase os="osuse">&opensuse;</phrase><phrase os="sles">&sls;</phrase><phrase os="sled">&sled;</phrase>'>
<!ENTITY productnamereg '<phrase os="osuse">&opensusereg;</phrase><phrase os="sles">&slsreg;</phrase><phrase os="sled">&sledreg;</phrase>'>
<!ENTITY productnumber '<phrase os="osuse">12.2</phrase><phrase os="sles;sled">11 SP2</phrase><phrase os="sled">11 SP2</phrase>'>
Where are they defined so that I can modify them manually and test if it really comes from there?
Guillaume
--
To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org
Hi,
the entities &productname; &productnamereg; and &productnumber; used to
be resolved by processing instructions, so the product is
automatically set to the value defined with the accompanying variables
in the DC-file.
Although this solution was very convenient, it needed a lot of code in
the SUSE stylesheets that was difficult to maintain. Therefore we
decided to drop that code with the latest version of the
suse-xsl-stylesheets (>= 1.9.6).
From now on the entities &productname; &productnamereg; and
&productnumber; need to be defined as follows in xml/entity-decl.ent:
-------------------
<!ENTITY productname '<phrase os="osuse">&opensuse;</phrase><phrase
os="sles">&sls;</phrase><phrase os="sled">&sled;</phrase>'>
<!ENTITY productnamereg '<phrase
os="osuse">&opensusereg;</phrase><phrase
os="sles">&slsreg;</phrase><phrase os="sled">&sledreg;</phrase>'>
<!ENTITY productnumber '<phrase os="osuse">12.1</phrase><phrase
os="sles;sled">11 SP2</phrase><phrase os="sled">11 SP2</phrase>'>
--------------------
The only drawback of this solution is that DocBook4/NovDoc does
not allow <phrase> in <literal> and <guimenu>, so you need to fix that
in (very few) places.
Note: The new solution is backwards compatible, so if you do not use
the latest SUSE stylesheets (as available from Documentation:Tools),
yet, switching to the new product* entities will not hurt.
--
Regards
Frank
Frank Sundermeyer, Technical Writer, Documentation
SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/
SUSE Linux Products GmbH, GF:
Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
"Reality is always controlled by the people who are most insane" Dogbert
--
To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org
What is the recommended format of terminal output?
I expect that <command></command><computeroutput></computeroutput> but
want to be in compliance with other authors.
Also, its been awhile since I wrote with novdoc; what
wrapping/hyphenation directives are available to authors? I've got
output that is 100-105 columns wide. Looks ugly on the pdf....simply
concatenates.
Thanks for your time.
--
Thomas R. Jones <trj(a)thomasrjones.com>