Best way to translate new pages intended for end users of slint website?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Also , to properly display translated manual pages that are encoded in UTF-8, insert one of following commands in your ~/.bashrc:
export GROFF_ENCODING=utf8 # If all man pages you read are either in English or encoded in UTF-8
alias uman="GROFF_ENCODING=utf8 man" # If you also read man pages in other encodings
But I don't see the red part into slint.txt on Transifex.
I think that each translation team should translate the top title and the left hand menu, but should be given the choice of which pages should be translated among those mostly intended for contributors (Contribute, Tools, Translators, ChangeLog).
So here is a proposal, that is a request for comments (hence removing the [SOLVED] status of thus thread):
I upload on Transifex pages menu.txt (including the left hand menu and the top title). All translation teams are request to translate it (should take less than 5 minutes :-)
Each team is requested priority translate menu.txt, installer.txt, package.txt and slint.txt. As soon as that's done I do the migration old home page => new home page.
I upload contribute.txt, tools.txt and changelog.txt. Each team may choose to translate or not some or all of theses files, that will be put on line as soon as complete.
A team choosing to translate changelog.txt should be ready to update that translation very soon after an update of the original, that will be displayed instead till the translation be updated.
I wish happy holidays and a happy new year to all.
Happy holidays to you too.
If you have a look at this bit on package.html.pl_PL:
wget http://slint.fr/packages/slint-14.1* # pobierzesz najnowszą wersję pakietu Slint wraz z towarzyszącym plikiem md5 md5sum -c Slint-14.1*md5 # jeśli odpowiedź nie jest "OK", pakiet może być uszkodzony su # uzyskaj prawa użytkownika root upgradepkg --install-new --reinstall Slint-14.1*txz # polecenie to instaluje bądź też aktualizuje pakiet
I am not able to split the commands over new lines. I've tried copying the original text and modifying it or writing it again from scratch - it keeps getting appended to the previous line. I've read that it's recommended to copy the source string to keep the formatting but that's what I've been doing with no luck.
Distribution: Slint64-14.2rc on Lenovo Thinkpad W520
@ sycamorex. In string # 9, you replaced the original "----" (four hyphens) with "____" (four underscores). Just copy/paste the source string to the translation instead, and all will be well.
Explanation: in asciidoc syntax, "----" marks beginning or end of a ListingBlock, "____" a QuoteBlock instead as stated here, and in an ordinary block (as in a quote one), appending " +" to a line is needed to generate a line break.
Rule of thumb: just copy/paste the (markup part of) the source string to the translation if you're not sure of its meaning
@ kooru: done, thank
Last edited by Didier Spaier; 12-25-2013 at 08:23 AM.
Reason: many typos corected + missing link added
So e.g. if your user agent is set to prioritize displaying Russian or Spanish content, simply typing URL http://slint.fr or http://slint.fr will display new home page in Russian or Spanish respectively.
Delivering different content under the same canonical URL is a bad idea. It's bad for search indexing and content caching. And almost no end-user knows how to change the (IMHO bogus) "Accept-Language" HTTP-Header in his browser configuration. Don't let me start on mobile browsers...
Best practice for international web sites is to use GeoIP detection for determining a language preset and then do a HTTP 302 redirect to the correct localized version under a distinct URI (like http://ru.slint.fr for example), accompanied by a visible option to immediately change the display language to a different one. All major players on the web handle it this way.