Imagine a spoiled son of a rich lawyer, with lots of whisky and some royal blood running through his veins, who is about to spend the last bits of the family fortune on 'Wein, Weib und Gesang', trying to get up from his chair at the bar, with the intention to deliver an unforgettable speech..that's more or less how the G-translation sounds _________________

Imagine a spoiled son of a rich lawyer, with lots of whisky and some royal blood running through his veins, who is about to spend the last bits of the family fortune on 'Wein, Weib und Gesang', trying to get up from his chair at the bar, with the intention to deliver an unforgettable speech..that's more or less how the G-translation sounds

Imagine a spoiled son of a rich lawyer, with lots of whisky and some royal blood running through his veins, who is about to spend the last bits of the family fortune on 'Wein, Weib und Gesang', trying to get up from his chair at the bar, with the intention to deliver an unforgettable speech..that's more or less how the G-translation sounds

Sounds great, maybe we can translate it back to English for en_US.

Automated translations from other languages are possible in version 0.5 now.
See example nl to en_US

a comprendre son utilisation et la différence avec gettext du point de vue de celui qui va traduire
to understand its use and the difference with gettext the point of view of one who will bring

ou il sauvegarde le fichier de langue qu'il crée, car sur cet capture d'image il n'y a pas de bouton d'enregistrement
and it saves the language file it creates, because of this image capture, it no record button

Pour l'instant, je préfère l'utilisation de gettext comme:
For now, I prefer to use gettext as:

shinobar Post subject: Is it easier? wrote:

Subject description: i think gettext is more simple and easy.
﻿As a conclusion, i do not think it is easier than using gettext.
gettext '.po' file can be edited by text editors. The original message is associated on the 'po' file.
But using the smert tools like poedit is more easier.

Voici les quelques points qui me pose quelque problème:
Here are some points that I have some problems:

Quote:

L18L PostPosted: 15 Nov 2011 11:32
To test the script completely you must do this as fido or spot.
I have run it in a real console (CTRL-ALT-F2, switch back to X by CTRL-ALT-F4):
login as root, then
su fido
pmount
This will ask for administrator's password using your translation.

les mots mentionné ne fonctionne pas chez moi
the words mentioned does not work for me

si oui pourriez vous fournir le nom d'utilisateur et le mot de passe
If so could you provide the username and password

Concernant les lignes a ajouté en tête du script, on trouve différentes version y compris dans le script t12s, quel est la bonne version
On the lines added at the top of the script, there are different versions including the script t12s, what is good version
﻿

Posted: Tue 31 Jan 2012, 08:30 Post subject:
Why t12s was not translated using... t12s?Subject description: ... This would have been the best example!

Hello,

Quote:

We regret that the script has not been internationalized

This would be indeed a very good example of what t12s, funny thing, cannot (yet) properly do!

I tried to do it but didn't succeed! I noticed that _M_ was identified as the beginning of chains to be translated, making t12s to be mistaken and generate corrupted tmp file...
Then, text using markup (<span></span>) seems causing problem too or at least, really complicate work if translator has to split text chains to turn it round. (As far as I know, this doesn't happen using gettext?).
Examples:

Code:

[ "`grep _M_ $myfile`" ] && break

Code:

<span color='red'>_M_</span>

Code:

...

I guess I actually don't see benefits translators can get from this way to internationalize applications compared to gettext and poeditor (or even the simpliest way I ever encountered: I mean the 'simple' script based on MU written by shinobar).

Cordialement._________________Last edited by Argolance on Wed 01 Feb 2012, 09:41; edited 7 times in total

The .po files are flat text files and the translators can post .po files using editors, but using poeditor or something is easier i guess.
T12s flat text files can be edited by using editors, but using t12s editor is better.
I cannot find any difference between the gettext and the t12s.

The point is which is familiar with the gettext or the t12s.
Anyway, the gettext is essential for Puppy applications and the t12s is not.

Hello vezuve,
sorry for this late reply I will try to answer your questions.

vezuve wrote:

a comprendre son utilisation et la différence avec gettext du point de vue de celui qui va traduire
to understand its use and the difference with gettext the point of view of one who will bring

ou il sauvegarde le fichier de langue qu'il crée, car sur cet capture d'image il n'y a pas de bouton d'enregistrement
and it saves the language file it creates, because of this image capture, it no record button

L18L PostPosted: 15 Nov 2011 11:32
To test the script completely you must do this as fido or spot.
I have run it in a real console (CTRL-ALT-F2, switch back to X by CTRL-ALT-F4):
login as root, then
su fido
pmount
This will ask for administrator's password using your translation.

les mots mentionné ne fonctionne pas chez moi
the words mentioned does not work for me

si oui pourriez vous fournir le nom d'utilisateur et le mot de passe
If so could you provide the username and password

The script askpass asks for root´s password if you are not root.

vezuve wrote:

[*]Concernant les lignes a ajouté en tête du script, on trouve différentes version y compris dans le script t12s, quel est la bonne version
On the lines added at the top of the script, there are different versions including the script t12s, what is good version

0.4.5.1 is in woof now.

vezuve wrote:

On regrette que le script na pas été internationalisé
We regret that the script has not been internationalized

Posted: Tue 07 Feb 2012, 16:16 Post subject:
Re: Why t12s was not translated using... t12s?Subject description: ... This would have been the best example!

Argolance wrote:

Hello,

Quote:

We regret that the script has not been internationalized

This would be indeed a very good example of what t12s, funny thing, cannot (yet) properly do!

I tried to do it but didn't succeed! I noticed that _M_ was identified as the beginning of chains to be translated, making t12s to be mistaken and generate corrupted tmp file...
Then, text using markup (<span></span>) seems causing problem too or at least, really complicate work if translator has to split text chains to turn it round. (As far as I know, this doesn't happen using gettext?).
Examples:

Code:

[ "`grep _M_ $myfile`" ] && break

Code:

<span color='red'>_M_</span>

Code:

...

I guess I actually don't see benefits translators can get from this way to internationalize applications compared to gettext and poeditor (or even the simpliest way I ever encountered: I mean the 'simple' script based on MU written by shinobar).

Cordialement.

It was never intended to internationalize t12s thus it does not work.
You have tried it?

If I try to run it I get a messages starting with
Sorry, could not....

Goal was not benefits for translators but speed of execution. Remember?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum