FT10 – Doubt about translation

[Member Spartak77]

I have a doubt about the translation of two sentences: No. 5 and 6 of the resource: FT10 TZ-Manager (this resource is contained in antix-contribs on Transifex)
These are the two sentences to translate:

$add_tz_text!add:FBTN
$delete_tz_text!remove:FBTN

Since the first part of each sentence is a formula, I think we don’t have to translate this part, but only the word after the colon (:), so the idea is to translate them in Italian like this:

$add_tz_text!aggiungi:FBTN
$delete_tz_text!rimuovi:FBTN

I saw that the French have translated

add_tz_text!ajouter:FBTN
$delete_tz_text!supprimer:FBTN

in an overlapping way to how I would intend to translate, however I have some doubts.

All the sentences about FT10 have been translated into Italian by madibi except for these two that have remained untranslated for a few days. We consulted and decided to ask for information on the forum. Today I saw Robin completed the translated sentences in Italian, with these two sentences, leaving them in English.
I guess Robin needed all the translated sentences to put them in the FT package, and therefore, not finding them translated, he left them as they are in the original English version.
Have I understood correctly?

Do I still have time to translate them?

Is it correct to translate only “add” and “remove” and leave everything else as in the original?

• This topic was modified 1 year, 3 months ago by Spartak77.

[Member PPC]

Helpful

Up

0

::

@Spartak77 – Thanks for your help in translating FT10! The translation is already 100% finished (I even translated the .desktop files, that are not it Transifex, so all menu entries related to FT10 should appear localized to PT, PT-BR, FR, ES, IT and DE).
I’ll be uploading the resulting .deb package to gitlab very soon (version 1.3beta), probably tonight, as soon as I add a menu entry to turn on and off the Visual Effects. I’ll let the users test this beta for a couple of days then update the source code and give anticapitalista the heads up, so he can create the final .deb package and send it to the repository (this means that as soon as any user that has FT10 v.1.2 installed updates antiX, V1.3 will be installed)
I’ll have to send the updated language files over to Robin, so he can insert translate the remaining languages via his script… But I’m too tired for that now…

Many thanks to the translation team!

P.

Edit: I just uploaded the .deb for FT10 version 1.3beta1, it’s over at https://gitlab.com/antix-contribs/ft10-transformation/-/blob/main/packages/ft10-transformation_1.3beta1_all.deb

• This reply was modified 1 year, 3 months ago by PPC.

[Member madibi]

Helpful

Up

0

::

@PPC – first of all I send you my best wishes regarding your health

my doubt concerning the 2 lines described by @Spartak, are based on the fact that they look as “programming instructions”, in this case I must let it as they are, because I could damage something. Otherwise I can translate (also if I don’t know what FBTN is 🙂 – may be you can provide an answer

another little doubt: is it correct to think that in order to have the new translations in my already installed FT10, I should only do a “sudo apt update”?

[Member PPC]

Helpful

Up

0

::

@madibi – I posted a complete “how to” install FT10 v. 1.3beta1 over at the main FT10 thread!

[Member Robin]

Helpful

Up

0

::

Hello @Spartak77,

You are right. These strings are obviously not meant for translation at all. Since I didn’t prepare the script files for creating the translation set, but only let run the string extractor on them, I noticed these entries erroneously marked for translation only when setting up the machine translation processing. I recognise them as part of yad form field syntax:

$add_tz_text!add:FBTN

This consists of three parts, non of which is translatable:

$add_tz_text is a bash variable, containing some kind of text string. You can’t translate the name, otherwise the script won’t work any longer, since the variable will not get recognised.

It is followed by !, an exclamation mark, which is a separator sign here used by yad.

add is an standard icon name (probably of GTK), and also not translatable, since all the icon names are in English by default as far as I know, even in foreign language systems.

And finally the part :FBTN is the field type for this yad field element.

As you can easily see, the other entry shows exactly the same structure, it is the same thing.

May be I’m wrong, but I do consider non of these entries to be translatable in any of their parts, which is the reason why I excluded them from automatic translation, and they are untranslated. They shouldn’t have been marked for translation within the script at all.

@PPC : You’ll have to be way more carefully when preparing scripts for translation. As I’ve proposed before, join #antiX-translators channel, I am willing to give you all support and advice in this task I can. Don’t expect me to know everything, but I have some experience in this task meanwhile you might profit from.

Windows is like a submarine. Open a window and serious problems will start.

[Member Spartak77]

Helpful

Up

0

::

Thanks Robin for the explanation, it’s all clear now.

[Member Wallon]

Helpful

Up

0

::

Dear PPC, Dear Robin,

I have just reread this thread and I am really ashamed to have let this pass in the translation into fr and fr_BE.
I have just corrected today, Wednesday 14 September 2022, two files in Transifex to put the variables back in English.

1st file: FT10 TZ-Manager
– string 5: “$add_tz_text!add:FBTN” changed to English.
– string 6: “$delete_tz_text!remove:FBTN” reset to English.

2nd file: FT10 Tint2 Top Bottom
– string 7: “$window_title” reset to English.

Is it possible to remake the *.mo files?

I am very sorry for all the inconvenience I am creating for you.

Best regards,
Wallon

• This reply was modified 7 months, 4 weeks ago by Wallon.

[Author]

Posts