search

sailfishos-chum / sailfishos-chum-gui

GUI application for utilising the SailfishOS:Chum community repository
https://openrepos.net/content/olf/sailfishoschum-gui-installer
MIT License
13 stars 17 forks source link

Updates for file translations/sailfishos-chum-gui.ts in it #308

Closed transifex-integration[bot] closed 2 months ago

transifex-integration[bot] commented 3 months ago

The following localization files have been updated:

Parameter Value
Source File translations/sailfishos-chum-gui.ts
Translation File translations/sailfishos-chum-gui-it.ts
Language Code it
Transifex Project SailfishOS:Chum GUI
Transifex Resource translations/sailfishos-chum-gui.ts (main)
Transifex Event translated
Grouping Resource-Language
legacychimera247 commented 3 months ago

Everything is good except for one single word

i wrote "librerire" on the very long phrase at the end of the translation, while the correct one is "librerie"

everything else is good

in my defense anyway, didn't want to cause so much trouble :p

Olf0 commented 3 months ago

i wrote "librerire" on the very long phrase at the end of the translation, while the correct one is "librerie"

Then rectify this at Transifex: This pull-request will become updated then.

in my defense anyway, didn't want to cause so much trouble :p

Well, I clearly denoted the common, easiest and fastest way of submitting and maintaining translations in the translations/README. You eagerly wanted to pose a pull-request directly (which the translations/README unambiguously discourages), because you believed it would be even faster, and hence caused a lot of work which implicitly slows the whole process down significantly.

General takeaway: If a FOSS project uses a translation platform, do not bypass it!

legacychimera247 commented 2 months ago

ok done, everything is good now

Olf0 commented 2 months ago

ok done

Thanks.

Now, at the weekend, I have a bit more time to review this, partially out of nosiness how good my Italian still is (cannot speak and hardly listen, but read well, because I learnt Latin for 5 years and read "easy language" newspapers when in Italy).

  1. Typos (search for these strings at Transifex in order to rectify them):

  2. Spelling of Sailfish OS You use Sailfish OS, Sailfish Os and Sailfish seemingly arbitrarily: Please consistently adhere to the original spelling Sailfish OS. See also next point no. 3. Side note: I usually spell it SailfishOS, which is the original spelling Jolla used in 2013 / 2014 but ceased to do so later. This also avoids inserting an NBSP, but the SailfishOS:Chum GUI app is a collaborative effort and the majority of us three developers voted for Sailfish OS to reflect Jolla's newer spelling.

  3. Just a check & balance question: I do not understand your consideration to place the non-breaking space characters ( ). The only purpose of NBSPs is to prevent a line break at this location, because a HTML renderer is free to insert a line break at any regular space character. Examples:

    • You write versioni di Sailfish OS many times, where I would (spontaneously) have written versioni di Sailfish OS.
    • una vrsione  di Sailfish uses an NBSP and a consecutive space, which is definitely wrong (and contains an example of both point 1 and 2).
    • There are many occurrences of these seemingly misplaced NBSPs, but maybe I simply do not understand the line of thoughts to place them this way, yet.

  4. SailfishOS:Chum GUI also has to be spelled exactly like this (with GUI in "all caps" = only using capitalised letters), because GUI stands for Graphical User Interface (i.e. it is a TLA (Three Letter Acronym)). You use SailfishOS:Chum Gui at least once, please rectify it.

  5. Tracker problemi per riportare problemi, … sounds a bit strange to me (i.e. the double problemi). In know issue is a tricky word to translate. What about "if in doubt, leave it out", i.e. Tracker per riportare problemi, … (just a question / suggestion, feel free to argue against it)? Though it might be better to find a more specific translation for bug reports / "reporting bugs" than riportare problemi, because "bugs" in this context are "software flaws" (or better: "flaws software has / shows / exhibits") not generic "problems". If you do, IMO the first problemi (in Tracker problemi per …) should stay. This would also much better align with your use of Problemi for Issues at four other locations, e.g. here.

  6. Here I am "leaning far out of the window" due to my little Italian proficiency: You translated as for Cbeta users with o per utenti beta, which I would retranslate to or for beta users. But "Cbeta" denotes the "closed beta" releases Jolla distributes to a small group of people outside of Jolla under NDA, before a new release of SailfishOS is published as "EA" ("early access") release (which is a "public beta") and then as "GA" ("general availability") release to all users. I.e. you cannot simply drop the "C". I also wonder about translating "as" (meaning "like" (colloquially) / "for example") with "o" which I would retranslate to "or", but I might simply not understand Italian well enough.

legacychimera247 commented 2 months ago

1 will fix those

2 ok, so what should i do? is " Sailfish OS " the correct way?

3 i didn't know what NBSP was standing for for so i just assumed it was some sort of highlighting and tried to make it like the original, will try to correct those but i guess i need to see it live to better understand

4 ok

5 i know it's not sounding good but that's just the way it is, can just only write "tracker per riportare problemi" then and will sound better and exact the same

6 didn't see the c at all

legacychimera247 commented 2 months ago

ok everything should be addressed now...

Olf0 commented 2 months ago

3

3 i didn't know what NBSP was standing for for so i just assumed it was some sort of highlighting and tried to make it like the original, will try to correct those but i guess i need to see it live to better understand

As I already pointed out, the HTML encoding   encodes a non breaking space character, hence there is nothing to see, only the absence of line-breaks at this location (as explained earlier).

2

2 ok, so what should i do? is " Sailfish\ OS " the correct way?

If you write HTML source text: yes. Here the strings become double-interpreted, hence also every & has to be encoded as & in the ts-file. I think (but am not sure) you have to input it at Transifex the way I denoted before: Sailfish OS Well, crucial is only what ends up in the ts-file, which definitely has to be Sailfish OS.

But now it is always Sailfish OS in the ts-file, for example in line 370: The second amp; in the middle is too much and has to be eliminated.

Furthermore, you still have some SailfishOs (i.e. with a small s), for example SailfishOs:Chum in line 375, SailfishOs:Chum:Testing in line 370, also line 381 and line 386, etc.

Line 427 still has della versione di Sailfish installata. which should be della versione di Sailfish OS installata.

[Line 544]() still has hardware e versioni di Sailfish OS. which should be hardware e versioni di Sailfish OS., architetture e versioni di Sailfish OS. which should be architetture hardware e versioni di Sailfish OS. (i.e. you also omitted the "hardware" here; IMO "architecture" without a specifier is ambiguous), and quali mancano nell'OBS di Sailfish OS. which should be quali mancano nell'OBS di Sailfish OS.. In this line there also is an SailfishOS:chum which I did not notice before and should be SailfishOS:Chum (with a capital C).

5

5 i know it's not sounding good but that's just the way it is, can just only write "tracker per riportare problemi" then and will sound better and exact the same

I should have deleted my initial consideration, because I later hoped you would focus on the second part of my statement:

Though it might be better to find a more specific translation for bug reports / "reporting bugs" than riportare problemi, because "bugs" in this context are "software flaws" (or better: "flaws software has / shows / exhibits") not generic "problems". If you do, IMO the first problemi (in Tracker problemi per …) should stay. This would also much better align with your use of Problemi for Issues at four other locations, e.g. here.

What about Tracker problemi per segnalazioni di bug, … or Tracker problemi per segnalare dei bug, … (sounds better than the first variant IMO) or Tracker problemi per riportare dei bug, … or something similar?

6

6 didn't see the c at all

Well, you solely addressed the c, but not the rest of my statement:

I also wonder about translating "as" (meaning "like" (colloquially) / "for example") with "o" which I would retranslate to "or", but I might simply not understand Italian well enough.

Here I really would like some feedback, because I would translate "o" always as "or". If I am wrong, I would like to know and learn something.

What about per gli utenti Cbeta or per esempio per gli utenti Cbeta?

Olf0 commented 2 months ago

After a more than a week without a response, I decided to …

  1. disable the Italian translation, see ac68257.
  2. merge this PR to let the main branch become synchronised with Transifex.

@legacychimera247, please fix the remaining flaws I described in detail (with suggestions how to resolve them) in https://github.com/sailfishos-chum/sailfishos-chum-gui/pull/308#issuecomment-2323476653 at Transifex. If all these points are addressed, I will re-enable the Italian translation again.