Best way to translate new pages intended for end users of slint website?

Didier Spaier · 12-30-2013, 12:28 PM

Agreed, thanks Yaroslav. I just wrote TIP instead of NOTE

Diantre · 12-31-2013, 05:59 PM

Hello again. This time I have a few suggestions for "tools.txt", bear with me...

Quote:

= Tools useful for Slint contributors

I'm nitpicking, I know, but the title sounds better to me as "Useful tools for Slint contributors"...

Quote:

Warning: If you prefer to translate locally, be sure to check in Transifex 'Download for translation'...

Just a question here, is that "Warning" intented as a normal paragraph, or should it be an AsciiDoc admonition as in "WARNING"?

Quote:

WARNING: Following an update of an original English text file, text strings in translation files that matched strings modified in the English file will disappear.

In that case you can save some typing if you kept a local copy of the translation (dowloding it from Transifex), so that you can copy the old translation from that local copy and paste it into Transifex editor, the editing it as need be.

Just a small typo: ...then editing it as need be...

You could mention here that the Transifex editor has a "Suggestions" feature (similar to the "Translation Memory" in Lokalize) where it "remembers" similar past translations of a string. This feature has been really useful for me whenever a website page gets updated. Transifex will remember my last translation of the string and present a "Use this" link next to the suggestion, so I just use it, avoid re-typing an re-translating, then modify it slightly, and on to the next one.

Quote:

In Transifex, you will see "raw" text strings, mixing formatting instructions for 'asciidoc' and content. Be careful to preserve instructions while translating content. It helps to know a bit of the specif syntax of formatting instructions, for instance looking at asciidoc's http://asciidoc.org/userguide.html[User Guide] or at the http://powerman.name/doc/asciidoc[Cheatsheet].

A small typo: ...a bit of the specific syntax...

Quote:

WARNING: To avoid messing with formatting instructions, we recommend that you first copy the source string (in English) to the translation (just click on the icon showing two pages on the upper left of the source string area) then edit it.

A question: Isn't the "Copy source string" icon in the upper right?

Quote:

* You can easily check the rendering of the web page generated from your translation of a source text file. Instructions to do that are provided in file http://slint.fr/website/README.TXT.

Other slint web pages display files as links, perhaps that was the intention in this case: http://slint.fr/website/README.TXT[README.TXT], or maybe not?

Quote:

TIP: To run the installer in a virtual machine you can use directly file ending in .iso as virtual media, no need to burn it on a physical media in that case.

Maybe this should read: ...you can use directly the file ending...

That's it, thanks for reading. And happy new year!

Didier Spaier · 12-31-2013, 06:09 PM

Thanks Diantre, I'll take care of that later today (1 AM here :-)

Meanwhile, your translation of this page in its current state is on line

j12i · 01-01-2014, 12:27 PM

Quote:

TIP: To run the installer in a virtual machine you can directly use the file ending in .iso as virtual medium, there is no need to burn it on a physical medium in that case.

fixd
media = plural of medium

Didier Spaier · 01-01-2014, 01:06 PM

Quote:

Originally Posted by someone named bert

media = plural of medium

Well, that's right but during Slackware installation "media" is used instead, e.g.

Quote:

Please select the media from which to install Slackware Linux:

so I'm not sure that we should use another spelling in Slint website.

sycamorex · 01-01-2014, 02:44 PM

Hi Didier. Just a couple of typos:

Changelog:

Quote:

Greek translation of slint.sh have been added. +

Quote:

The Changelog retracing changes that occured

Thanks

Didier Spaier · 01-01-2014, 04:22 PM

@sycamorex: fixed (plus another one I just found :-), thanks Marcin.

Didier Spaier · 01-01-2014, 04:34 PM

I promised to write an How-To about AsciiDoc syntax before end of 2013. I am one day (or one year :-) late but it's done, see How-to translate a document in AsciiDoc format.

To be honest content is very small and I'm not sure that deserves an article.

So in addition I added that content to page Tools on the website (also edited to apply suggestions from Diantre).

That'll give some more work to people who already translated it, so I hope that won't make them too angry

PS: feel free to suggest more enhancements to web pages, either posting them here or just sending me edited source .txt file or a diff against it.

Diantre · 01-02-2014, 06:03 PM

Quote:

Originally Posted by Didier Spaier

That'll give some more work to people who already translated it, so I hope that won't make them too angry

Angry? I'm furious! I'm so mad that I have more suggestions!!!

Just kidding, but I really have a few suggestions for tools.txt:

Quote:

wget http://slint.fr/slint.conf.ll; CONFIG_FILE=slint.conf.ll # replace "ll" with your language code (two digits)

I'd suggest "letters" instead of "digits" (numbers): ...replace "ll" with your language code (two letters)...

Quote:

Following words have a special meaning for Transifex and should not be translated when they begin an admonition paragraph (and are often replaced by icons): TIP, NOTE, IMPORTANT, WARNING and CAUTION.

Shouldn't that be AsciiDoc instead of Transifex?: ...have a special meaning for AsciiDoc...

Quote:

Generally speaking, links and URLs should not be translated, but associated caption may, depending on the context. In following examples (taken from output of 'ascii doc --help syntax') only value of 'caption' may be translated:

A space in the middle of "asciidoc": ...(taken from output of 'asciidoc --help syntax')...

A suggestion: ...only the value of 'caption' may be translated...

That's all...

Didier Spaier · 01-03-2014, 11:30 AM

@Diantre: fixed, thanks.

@yars: in contribute.ru.txt I added a missing "* " before "В зависимости от объема работы и доступных ресурсов,..."

Oh, and as rebuilding the whole website (only new pages, 38 at time of writing) with build-slint-website.sh takes less than 1min20s, new translations are still welcome

sycamorex · 01-06-2014, 05:30 PM

Hi Didier,

Contribute:

Quote:

Our link:index.html[old home page] have been written directly in xhtm

Thanks

Didier Spaier · 01-06-2014, 05:40 PM

Hi Marcin,

fixed and uploaded on Transifex, thanks

j12i · 01-07-2014, 05:49 AM

it is really unnerving that this forum will not allow nesting quotes...

Quote:

Originally Posted by Didier Spaier

Well, that's right but during Slackware installation "media" is used instead, e.g.

so I'm not sure that we should use another spelling in Slint website.

Quote:

Please select the media from which to install Slackware Linux:

Note that this could be plural as well, as you can install from a set of CDs/DVDs

Didier Spaier · 01-07-2014, 08:57 AM

Quote:

Originally Posted by someone named bert

Note that this could be plural as well, as you can install from a set of CDs/DVDs

Yes. But elsewhere in the installer (in script INSdir) I see:

Quote:

You may install from any part of the current directory structure, no matter what the media is (including NFS).

Nonetheless don't worry, I will change the wording of the sentence that hurts your eyes.

Didier Spaier · 02-14-2014, 01:20 PM

I changed the website's layout.

Now all pages are in a per language subdirectory including English, e.g. ru/tools.html, de/tools.html, en/tools.html.

Also, all pages include links to all available localized versions of that page (not all pages are translated yet).

When a user choose a language clicking in such a link, we save that choice in a cookie. If the cookie exists we send next requested pages in the same language, if available, else in English
If there is no cookie for whatever reason, we send all pages in a language found in Accept-Language, if available, else in English.

I didn't find a way to store user's choice of language in the server not using a server side script, so that'll stay so for the time being. I considered storing it in an Apache variable, but AFAIK the name of such a variable can only be a static text string, not e.g. include %{REMOTE_ADDR}.

You can check how these settings are done looking at attached file.

I welcome in advance any criticism or suggestion for enhancement.