Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use different source string IDs for "On" and "Off" in the Preferences panel #55

Open
AlessandroMenti opened this issue Sep 2, 2016 · 6 comments

Comments

@AlessandroMenti
Copy link
Contributor

AlessandroMenti commented Sep 2, 2016

The Italian translations of "On" and "Off" ("attivato" and "disattivato") follow the gender and number of the name they refer to.

This, therefore, requires separate source string IDs to be used in the Preferences panel - at least two for "On" and "Off" in the Automatic Updates box, another two for the Print Preview box and another two for the System Hotkey box.

It would be even better to have four of them for each box:

  • two to state the present condition of each feature ("active"/"attivato" or "inactive"/"disattivato");
  • another two for the command buttons that change the state, where a verb is more suited for that purpose ("activate"/"attiva" and "deactivate"/"disattiva").
@Noitidart
Copy link
Owner

Thank you very much for jumping onto Github!! :)

@TheRabbitter
Copy link

I have had the same problem in Catalan (and that applies also to Spanish and probably other languages). I would suggest to have four strings just as Alessandro did. In our language you need a word for its present state ("Activat"/"Enabled") and another to the action of changing its state ("Activar"/"To enable").

@Noitidart
Copy link
Owner

Ah that's cool so this change will apply to multiple languages.

@Noitidart
Copy link
Owner

Noitidart commented Sep 13, 2016

So I tried addressing this today. I was releasing emeregency release v1.10 and wanted to include this awesome work by you all!

When I make the change its adding 8 new strings and removing 2. The major issue though is - I have a templating function, I tell it I need X prefs. It creates blocks for each one in the GUI. It creates buttons that have event listeners attached for toggling. I tried making the change but it broke in the history page as the same templating function is used in multiple places there (independent of the pref/title it is localizing).

In the Urdu and English we don't have number but we have gender but we apply masculine if its possible it can be either one. Like "air hostess" on airplane, but because they can be mlae we apply "air host" to all. It understood. Is this the same for Catalan, Italian, and Spanish? Or does it make it totally non-understandable due to the number?

I was hoping to push this fix to a later date unless it makes it non-understandable.

@AlessandroMenti
Copy link
Contributor Author

In Italian, that's not an option if I use the recommended translations "attivato" and "disattivato" - the "use the masculine gender" role you mentioned applies only if an adjective/participle applies to multiple objects at the same time (following your example: "Le hostess e gli steward a bordo sono alti" = "The female and male flight attendants aboard [this plane] are tall"; I use the masculine gender in the adjective "alti" because I'm applying the same characterization "tall" to all of them - both male and female - in a single sentence). Since each setting is controlled by their own button (and, furthermore, its description and switch are enclosed in a single group box), that rule is definitely not applicable.

An option might be keeping "On" and "Off" which are gender-neutral, even though they do not carry the distinction between

  • expressing the current state of the setting vs.
  • defining the state toggling action

I mentioned in the original comment (and are therefore, in my view, not optimal).

@Noitidart
Copy link
Owner

Noitidart commented Sep 13, 2016

Ah very interesting. I think I get it now. Ok I think I can flatten out the side effects without reworking, I'll keep you updated. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants