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

Decide on helper word usage #5

Closed
splewako opened this Issue Mar 11, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@splewako
Member

splewako commented Mar 11, 2016

This started as discussion in piotrdrag/mozilla-l10n-pl@4ee10c8

We should decide what we would like to support and what not when deciding to use or not helper words.

In shared parts like toolkit/ we cannot assume anything about gender obviously but should we take into account unofficial, development and different organization versions when translating application specific things? This seems especially pressing on anything but desktop where we have very limited space available.

@splewako splewako added the question label Jul 28, 2016

@splewako splewako removed the question label Aug 28, 2017

@splewako

This comment has been minimized.

Show comment
Hide comment
@splewako

splewako Oct 12, 2017

Member

I think we shouldn't take into account other branding. Mozilla doesn't seem interested in external codebase reuse and even internally, l10n is not prepared to accommodate random changes outside teams knowledge (against rules, length, gender, meaning). Example:

-# L10n note (string): %S will be replaced by app brand, i.e. 'Firefox'
+# L10n note (string): %S will be replaced by app brand, i.e. 'Firefox for iOS app'
 string=Aplikacja %S na iOSa

What's more, everything (builds from branches other than release) seems to contain main brand now (see bugs 1367912 and 1378834 - apparently reasons to name it differently were ignored).

Unfortunately in shared parts we cannot avoid (that could be the best solution) using brand placeholders/identifiers with helper words and we need to watch for changes and guess/test their impact anyway.

For parts that are not shared I suggest to keep placeholders only if they don't make translation longer or less natural sounding and ignore other problems (test branch brand gender etc) when keeping them.

Member

splewako commented Oct 12, 2017

I think we shouldn't take into account other branding. Mozilla doesn't seem interested in external codebase reuse and even internally, l10n is not prepared to accommodate random changes outside teams knowledge (against rules, length, gender, meaning). Example:

-# L10n note (string): %S will be replaced by app brand, i.e. 'Firefox'
+# L10n note (string): %S will be replaced by app brand, i.e. 'Firefox for iOS app'
 string=Aplikacja %S na iOSa

What's more, everything (builds from branches other than release) seems to contain main brand now (see bugs 1367912 and 1378834 - apparently reasons to name it differently were ignored).

Unfortunately in shared parts we cannot avoid (that could be the best solution) using brand placeholders/identifiers with helper words and we need to watch for changes and guess/test their impact anyway.

For parts that are not shared I suggest to keep placeholders only if they don't make translation longer or less natural sounding and ignore other problems (test branch brand gender etc) when keeping them.

splewako added a commit to splewako/mozilla-l10n-central-pl that referenced this issue Oct 30, 2017

splewako added a commit to aviarypl/mozilla-l10n-pl that referenced this issue Oct 30, 2017

@splewako splewako closed this May 10, 2018

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