@ jtsn: thanks for your post, I need some time to properly answer it.

... And on line

No problem. As a reminder, any translator registered on Transifex receives notifications for updates of files in a project as soon as he or she checks that option in Notification settings. This way you (and other members of Russian team) will know that an update is needed.

About {contribute,tools}.txt, I will wait a few days (till I receive answers to my request for comments) before uploading them. About menu.txt I have to find out the best way to format it, I hope it'll be done tomorrow night.

At the moment I'm not worried that much by search indexing of our web pages. And content caching is not really an issue here as our heaviest page weighs exactly 18,105 bytes

We can give end-users some clues to set it as a link to this page. Also, in many cases this header is already properly set by default as it matches either language of localized OS or localized browser.

About "bogus": I have no opinion there, but in any case alas I can change neither RFC 2616 § 14.4 Accept-Language nor implementations of this specification by software vendors

I have to disagree here. For instance in a lot of places in the USA you'll find that a near majority of people whose native language is Spanish (Latin America), but GeoIP will make us serve pages in US English, I assume.

My web hosting plan allows me to use as many sub-domains as I want, but I have still to find how to properly use this feature, for instance storing Russian version of package.html.ru http://ru.slint.fr/package.html? Would that allow better search indexing and caching that what I do currently, i.e. store that page as http://slint.fr/package.html.ru ?
Well, slint won't probably become a major player anytime soon... And for website maintenance (to which I can't devote a lot of time) I'm happy just generating static xhtml pages.

Using GeoIP localization for slint.fr would mean:

* install the GeoIP app (not even sure I can do that on my shared hosting plan)
* access the free database from MaxMind, probably not as accurate as the non free one
* add some PHP code that I'll have to maintain
* a slightly slower website

Thats' not worth the hassle for slint.fr IMHO.

Slightly out of topic: this discussion reminds me of Proposed Specifications For Languages Holding I wrote a few years ago for WackoWiki. Displaying an UI or serving web pages in the proper language is not as easy as it could seem...

PS I forgot to comment this:Agreed, with or without GeoiIP this is useful. We have that on top of the "old" home pages. I just have to figure out where it will best fit on the new web pages. And now list of available languages differ upon page displayed, I will have to take care of that too.

Sounds fine to me, Didier. I'll start translating as soon as the pages are available on Transifex.

@ translators: eventually, template.po (name I chose instead of menu.txt as that's actually a PO file used to generate the template for all new pages with po4a) is uploaded on Transifex and ready for translation. Each and every string is commented, so you should know what to do

So you want to make web pages that nobody will find using search engines?

BTW: Caching has nothing to do with size at all. But with transparent proxies (they are everythere) caching one version for one user and then delivering it to another one.

You want to make stuff complicated for users instead of just providing a page header with en|es|fr|ru and so on? Did have ever have to deal with a situation, in that you may not even be allowed to change the configuration of the browser you're currently using?

HTTP has a lot of features, which are not used, because they're not practical. Have you ever seen someone using HTTP 402 Payment required?

Everything that identifies a resource to be accessed has to be in the canonical URL.

This is not about forcing a language to someone, but start with a good guess and then allow the user to change it. Non-native speakers are everywhere, not only in the US.

It is irrelevant under which filename you store something. It counts what the webserver returns on a You won't have to use sub-domains, you also can use subdirectories like /ru/package.html. But make them visible to the clients and provide links to allow changing to a different one.

Further reading:

http://www.w3.org/International/ques...t-lang-locales
https://bugzilla.mozilla.org/show_bug.cgi?id=572667

1 members found this post helpful.

Some updates:

• The menu and the title in the blue header are translated (if translation of template.po is available).
• Available languages for the displayed page are shown between the blue header and the main title if other languages than English are available for that page, so that user can just click e.g. on "ru" to display the page in Russian.

Comments are still welcome.

@yars: please try to find a shorter translation than "Исходный код страницы" for "Page source" in template.po so that the translation fits on one line in the menu.

@jtsn: I have read pages you linked me to and this discussion is interesting, thanks. For the time being we will continue to use the Accept-Language header, but at least language can now be chosen easily on each page.

Remaining open issue is indexation by search engines. Would that help to redirect localized pages, e.g. http://slint.fr/package.html.es => http://slint.fr/es/package.html?

That can be done several ways, I assume:

• hard or soft linking the former to the latter
• using rewrite rules in .htaccess
• through PHP code (I'd prefer to avoid that if possible)

What do you think?

@Translators and coordinators: please communicate through relevant media in your locale about availability of the website in your language when you're ready.

@ Didier: Done, also home page (slint.txt) needs updating. On this page one string has incomplete translation.
When I browse the site, all the pages are available, but if I choose the link to the untranslated page (for example, the Contribute page) the left sidebar and the top title change the its language to English, and links to another languages disappear. It's bug?

Even if that looks weird, it's the intended behavior:

• When pages were generated (time indicated in page's footer) , there was no translation of Contribute available, hence no links to other languages to display on this page.
• Left sidebar and title are displayed in the language of currently displayed page. Contribute being only in English for the time being, that's English.

You can do two things to enhance the situation:

• Keep the English name of pages in the left sidebar (in your template.po), till they are translated in your language. That way visitors won't be surprised to see these pages in English.
• Translate theses pages (yes I know, they're not yet uploaded on Transifex, but it'll be done within 48 hours after I re-check them carefully :-).

1 members found this post helpful.

Okay, no problem Let it continue to remain.
Obviously, I choose a 2nd variant I can to wait.

Go!

PS Pages Contribute and Tools have been updated

@ Didier: typo in Contribute page: Maybe you want to say, "...in package linuxdoc-tools"?

1 members found this post helpful.

@ yars: yes, fixed, thanks.

Hello. I just finished translating "contribute.txt" and have a few suggestions:


Maybe it should say: "...should be given priority..." or "...should be translated with priority...".



Just a typo: template.po



That probably should read: "...that at least one person..."


I'm sorry, perhaps it's just me, but this phrase is slightly confusing. I'd express it differently, maybe like:

The translation text should include a "new line" character (or line feed, represented by "\n") at the beginning or at the end, exactly as the original text does. Conversely, if the original text doesn't have the character, then the translation shouldn't have it.

Or,

If the original text contains a "new line" character (also called "line feed", represented by "\n") at the beginning or at the end, the translation should also include it.

I'd remove the last dot, all other headers don't have it.


Just an uppercase "A" as in "A single backslash..."

1 members found this post helpful.

Thanks Diantre, page updated in Transifex.

I firsts uploaded http://slint.fr/contribute.html.es in its current state so that you can easily get back old translations of edited strings.

Didier, in the phrase from tools.txt, maybe the "Note" should be a tag "NOTE" for asciidoc?
And in this file, we have a duplicated strings:
1) 2) The 1) need to remove?

1 members found this post helpful.