[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Updated kcontrol modules.
From:       "Erik K. Pedersen" <epedersen () stny ! rr ! com>
Date:       2000-11-26 17:31:36
[Download RAW message or body]

Well I basically know how to translate the docs, but I don't know how to 
check my translations. My script that converted docbook to html 
says

#!/bin/sh
jw  -o HTML -c /opt/kde2/share/apps/ksgmltools/kde.cat  -d 
/opt/kde2/share/apps/ksgmltools/stylesheets/kde.dsl#html $1  

but that was from a time when I had one of Molnars tarballs installed. I 
suppose jw must live in some rpm somewhere. On a redhat 7 system today I 
suppose it should be

#!/bin/sh
jw  -o HTML -c /usr/share/apps/ksgmltools/kde.catalog  -d 
/usr/share/apps/ksgmltools/stylesheets/kde-l1da.dsl#html $1

or something close to that?  

On Søndag 26 November 2000 11:04, Frederik Fouvry wrote:
> ,-- On Sat, 25 Nov, Erik K. Pedersen wrote:
> | I used to be able to translate documents, but now I can not anymore. I
> | don't understand the instructions at i18n.kde.org, I compiled kdesdk, but
> | as far as
>
> ksgmltools, if that was what you were looking for, moved to kdelibs
> about a century ago ;-) The translation howto has not been updated
> since (the document does not contain a date, contrary to current
> guidelines ;-), and was generated using the style sheets version 1.44.
> The version we're using now is 1.57 or higher.  The editorial team
> mentioned on that page has been in full swing for about half a year
> now I think, and updated _loads_ of documentation.  Just to tell you
> that the document is lagging behind a bit ...
>
> Strictly speaking you don't need ksgmltools for translation though.
> But everyone appreciates documentation in valid SGML, so validating it
> (SGML errors; use nsgmls) or converting it (style, translation
> mistakes, ...; use kdb2html) is helpful.  [The conversion does also
> validation but takes a lot longer.]  BTW: invalid markup may cause
> documentation not to be available for the user ...
>
> Questions about the markup (what to change) may be answered in the
> translation howto, but quite a few things are outdated.  Check out
> http://i18n.kde.org/teams/en/, which is mainly for authors, but
> translators might find it helpful too.  Address remaining questions
> about the markup to the kde-DocBook list (see below).
>
> In short:
> 1. Don't touch the markup;
> 2. you may translate the value of the id attribute in markup, EXCEPT
>    when it is the id of an anchor (<anchor id="xxx"> - if you do
>    change it you'll break help functions);
> 3. you must change the language in the prologue (and only there):
>    <!ENTITY % English "INCLUDE" -- change language only here -->
>    to
>    <!ENTITY % Danish "INCLUDE">
> 4. add copyright for translators and update the author's section with
>    <othercredit role="translator">
>     ...
>     <contrib>translator-in-whatever-language-you-translate-for</contrib>
>    </othercredit>
> 5. update credits section at the end
> 6. general entities that contain English text (like &eg; for "e.g."
>    etc.) must be translated, so the entities should be replaced by the
>    translation in your language.
>
> | I can tell that does not help me, the i18n.kde.org page seems to contain
> | less information than it used to. The various things I do with cvs I
> | learned from there, but those pages are not there anymore, and the
> | rep[lacements contain less information
>
> A markup page for translators is indeed lacking as yet ...

[prev in list] [next in list] [prev in thread] [next in thread]