9:23 p.m.
Hi
I've been asked from someone that where is the file for translation of
Index page located [1]. It can be found at
https://translate.fedoraproject.org/projects/p/publican/c/trunk/.
[1]:http://docs.fedoraproject.org/ja-JP/index.html
noriko
10:03 p.m.
On 09/01/2010 12:23 PM, noriko wrote:
I've been asked from someone that where is the file for
translation of
Index page located [1]. It can be found at
https://translate.fedoraproject.org/projects/p/publican/c/trunk/.
[1]:http://docs.fedoraproject.org/ja-JP/index.html
That's not quite the whole picture...
The index page contains a elements from a number of different files:
* the main "welcome" text (in the main window) is in:
https://translate.fedoraproject.org/projects/p/docsite-publican/c/master/
* the navigation buttons in the navigation frame (like "Map",
"Search",
"collapse all") are in:
https://translate.fedoraproject.org/projects/p/publican/c/trunk/ (like
Noriko says)
* the "Technology" page that is linked from the navigation frame[0] is
in: https://translate.fedoraproject.org/projects/p/publican/c/site_tech/
Maybe this information should be added to the "Translating Websites"
section of the TQSG?
Cheers
Rudi
[0] for example, http://docs.fedoraproject.org/en-US/Site_Tech.html
10:41 p.m.
On 09/01/2010 01:13 PM, Yulia Poyarkova wrote:
Very useful info, thank you for clarifying that.
I just have one more question, will the website reflect translation changes
automatically ?
Unfortunately not. More specifically:
* Anyone in the docs-publishers group can update the welcome text
itself, by republishing the "docsite-publican" text. Normally, someone
in Docs will do this within a day or two of a translation being
completed or updated, but any translators ready to take care of their
own pages can do so too -- just email me and I'm happy to show you what
to do. (Spanish, Dutch, and Portuguese teams already do this)
* Changes to the navigation buttons and the Site Tech page are built
into Publican, and will appear automatically after a new version of
Publican is released and any book is published or republished in that
language. We expect to release a new version of Publican in the next few
weeks, so now is a good time to add new translations!
Note that you do not need to translate the whole of the Publican trunk
to translate the website buttons -- you could just translate the strings
marked "WebSite.pm" (about 15-16 strings, mostly one or two words).
However, if you do translate the whole Publican trunk, you can have the
Publican UI in your own language at the command line in future :)
Cheers
Rudi
11:54 p.m.
On Wednesday, 1 בSeptember 2010 06:41:28 Ruediger Landmann wrote:
* Anyone in the docs-publishers group can update the welcome text
itself, by republishing the "docsite-publican" text. Normally, someone
in Docs will do this within a day or two of a translation being
completed or updated, but any translators ready to take care of their
own pages can do so too -- just email me and I'm happy to show you what
to do. (Spanish, Dutch, and Portuguese teams already do this)
* Changes to the navigation buttons and the Site Tech page are built
into Publican, and will appear automatically after a new version of
Publican is released and any book is published or republished in that
language. We expect to release a new version of Publican in the next few
weeks, so now is a good time to add new translations!
Can the "Links to other parts of the Fedora Project site" point to correct
translation? This is so that someone reading the index page in (say) "he-IL"
and clicks the "Get Fedora" link, would be redirected to the "he"
version
of the page?
[BTW: we now have 3 language designators: "he_IL" (glibc), "he-IL"
(publican)
and "he" (Fedora website)....]
--
Oron Peled Voice: +972-4-8228492
oron(a)actcom.co.il http://users.actcom.co.il/~oron
Q: How many NSA agents does it take to replace a lightbulb?
A: dSva7DrYiY24yeTItKyyogFXD5gRuoRqPNQ9v6WCLLywZPINlu!
1:26 a.m.
On 09/01/2010 02:54 PM, Oron Peled wrote:
Can the "Links to other parts of the Fedora Project site"
point to correct
translation? This is so that someone reading the index page in (say) "he-IL"
and clicks the "Get Fedora" link, would be redirected to the "he"
version
of the page?
Yes absolutely -- this is up to translators, however. So, in the
"Welcome.po" file for docsite-publican, all you need to do is include
the localized URL in your translation:
#. Tag: para
#, no-c-format
msgid "Get Fedora: <ulink
url=\"http://fedoraproject.org/get-fedora.html\" />"
msgstr "הורדת פדורה: <ulink
url=\"http://fedoraproject.org/he/get-fedora.html\" />"
Note the difference in the URLs.
If you'd like to update the Hebrew PO files, I'll make sure they get
published.
[BTW: we now have 3 language designators: "he_IL" (glibc),
"he-IL" (publican)
and "he" (Fedora website)....]
Indeed. However, note that "he-IL" is not a Publican designation; it's
the designation from the XML standard.[0] Since Publican is an XML
authoring and publication tool, it meets the standards for that language.
Cheers
Rudi
[0] http://www.w3.org/TR/REC-xml/#sec-lang-tag
4:09 p.m.
On Wed, Sep 01, 2010 at 01:41:28PM +1000, Ruediger Landmann wrote:
On 09/01/2010 01:13 PM, Yulia Poyarkova wrote:
> Very useful info, thank you for clarifying that.
> I just have one more question, will the website reflect translation changes
> automatically ?
Unfortunately not. More specifically:
* Anyone in the docs-publishers group can update the welcome text
itself, by republishing the "docsite-publican" text. Normally, someone
in Docs will do this within a day or two of a translation being
completed or updated, but any translators ready to take care of their
own pages can do so too -- just email me and I'm happy to show you what
to do. (Spanish, Dutch, and Portuguese teams already do this)
* Changes to the navigation buttons and the Site Tech page are built
into Publican, and will appear automatically after a new version of
Publican is released and any book is published or republished in that
language. We expect to release a new version of Publican in the next few
weeks, so now is a good time to add new translations!
Note that you do not need to translate the whole of the Publican trunk
to translate the website buttons -- you could just translate the strings
marked "WebSite.pm" (about 15-16 strings, mostly one or two words).
However, if you do translate the whole Publican trunk, you can have the
Publican UI in your own language at the command line in future :)
I am asking for another project: How do you generate the .pot files
from the index.html file, and how do you generate the resulting language
index.html files?
best regards
Keld
11:03 p.m.
2010/9/1 Keld Jørn Simonsen <keld(a)keldix.com>:
I am asking for another project: How do you generate the .pot files
from the index.html file, and how do you generate the resulting language
index.html files?
html2po
http://translate.sourceforge.net/wiki/toolkit/html2po
12:57 a.m.
On 09/02/2010 07:09 AM, Keld Jørn Simonsen wrote:
I am asking for another project: How do you generate the .pot files
from the index.html file, and how do you generate the resulting language
index.html files?
Hi Keld --
Actually, we do something a little different:
The source (English) version of the text is in a DocBook XML file.[0] We
use a tool called Publican[1] to generate POT files and PO files for
that XML file.
When we publish, Publican transforms the XML into HTML, and when we
publish in a language other than English, Publican applies the PO file
to the XML before transformation.
Publican also builds and maintains the website structure and navigation
elements.
This process ensures that we only have one single source for any
document, regardless of how many formats we publish it in, and that
changes are easily propagated throughout the PO files for all languages
in a (semi) automated fashion. Depending on the nature of your project,
this might be overkill :)
Cheers
Rudi
[0] for example, see here:
http://git.fedorahosted.org/git/?p=docs/docsite-publican.git;a=blob;f=en-...
[1] http://docs.fedoraproject.org/en-US/Site_Tech.html
4985
days inactive
4986
days old
8 comments
6 participants
participants (6)
-
Domingo Becker -
keld＠keldix.com -
Noriko Mizumoto -
Oron Peled -
Ruediger Landmann -
Yuliya Poyarkova