Best way to translate new pages intended for end users of slint website?
Among others, Slint's website project has new pages intended for end users, as announced in this other thread:
Home, Slint installer and Slint package. These pages need to be translated in at least languages available in Slint installer (French, German, Polish, Portuguese, Russian and Spanish at time of writing, at least one other coming soon). They are generated using "asciidoc" (included in Slackware), from source files that you can display in clicking "Page Source" on each of them. I tried to make PO files of both source files and corresponding web pages using application "po4a" but was not satisfied of the result. So here is my proposal:
PS I will make some tries with Transifex but you may wait to use files there that we agree on the procedure and bugs are fixed in the web pages in English. By the way, please all readers report in this thread all bugs, typos, and other suggested edits to these pages that you can see. English is still not my native language... |
Quote:
Quote:
Some more: Quote:
A Slint package contains ... or Slint packages contain ... Quote:
At the time of writing the following languages ... Quote:
are also translated to other languages There's more, but it's too stressful this way, I'll wait for the proper source files. |
I liked the idea of using asciidoc as source for the web pages. I've nerver used it, but it seems to be very extensible and versatile.
I'm only worried with the propagation of modifications in the english originals. It may be hard for translators to identify what has really changed. What are the plans for that? |
Quote:
|
@ someone named bert: all fixed, thanks.
|
Quote:
@ Yars: as you're done translating this one, maybe you could participate in testing? |
The show can go on, but please wait a moment.
Here are my findings.
To do that I'll just have to rewrite all web pages' names in asciidoc files, removing the ".html" extension (including in the menu). EDIT: no, in fact I just had to rename English pages as <pagename>.html.en, and name localized ones <pagename>.html.<otherlanguagecode>, all links still ending in .html. Oh well, I should have remembered that... I'll need some time to do these changes and write specific instructions, so please don't hurry to translate if you want to avoid further editing. In the mean time, please report corrections to English pages that are still needed. |
@ Didier: Yes, I can to participate. Another bug found:
Code:
|setconsolefont|Configure the console mouse support |
@ Yaroslav. I can't say a thing about translation in Russian but at least your page looks good and links in it work, so thanks!
Thanks for the bug report as well, I'll fix it soon. EDIT. Done. Keep up the good work :cool: |
@ Didier:
please note repeated "if" typo "If if you had ..." in package.txt on Transifex. |
@ bormant:
Fixed on Transifex and on the website, thanks Serg. @ All: Tip: Such a change erase corresponding string in translation files, but you can copy old version of translated string from translated page on the website, paste it to Transifex and edit it if need be. |
Possibly I found a typo in the contribute.txt (currently I will do translation it) : "Slint package but man pages". Maybe this should be "Slint package but without man pages"?
Also, in the package.txt in which text "...be careful to check 'only' those whose names contains \'slint\'" the 2nd backslash is not needed, that is displayed on the web site as "'slint\'". |
Quote:
Quote:
I'd suggest priority translate pages intended for end users, that I will upload on Transifex in a few minutes and that will be named slint.txt (the new home page) and installer.txt, in addition to package.txt. As soon as each team will be done translating those three (slint.txt, installer.txt and package.txt) I will do a "migration", renaming for instance slint.ru.html to index.ru.html. This way people accessing the website either from index.html.ru, or from index.html with their browser set to prioritize Russian language, will directly access new pages. EDIT, previous sentence corrected, e.g.s/slint.html/index.html). Also, I'm now editing contribute.txt and tools.txt to add a few instructions for asciidoc files. In my opinion for pages that are being intended for translators (Contribute, Tools, and Translators), translation in not mandatory. Advices on that? |
Quote:
Quote:
|
Quote:
@ All: I am done including instructions and tips for these pages in Contribute and Tools and three files are uploaded on Transifex (remaining ones will come a little later), so I'm marking this thread as [SOLVED]. |
All times are GMT -5. The time now is 12:18 AM. |