word forms for terms.Bugzilla needed

[Vitaly Fedrushkov]

Necmettin Begiter wrote:
[quoted in full as crossposted to localizers at bugzilla.org]
> Hello all, I'm new to this list (but not Bugzilla translation). I am a
> developer working for the Pardus GNU/Linux project and I've just recently
> started translation Bugzilla 3.2 into Turkish as we will switch to 3.2 as
> soon as I'm done.

> First, some background information to the issue:
> Turkish language has two very interesting features that makes it a IMHO very
> un-mechanical language: Its written and spoken form is the same and the
> letters (=sounds) used in suffixes in word formation differs according to
> the letters (=sounds) preceding the letters to be added. Let me explain
> them in the simplest form I can:

> It's written and spoken form is the same:
> Ali is read as /ali/ (=Alpha Lima India)
> Book is read as /book/ (consider the /o/s in door)

> On to the second issue, different letters (=sounds) in the suffix for words
> with different endings:
> Bugzilla'nın (=Bugzilla's)
> Ali'nin (=Ali's)
> Notice the "nın"-"nin" difference here.
> Bugzilla'da (=in Bugzilla)
> Eskişehir'de (=in Eskişehir)
> Also notice the "da"-"de" difference here.

Siarhei once provided a similar example, which leads to terms.bug customizarion 
being useless in Belarusian due to long distance dependencies, even in 
situations where gender is not changed.

> The conclusion:
> I need to add variables like terms.BugzillaNom, BugzillaAcc, BugzillaDat,
> BugzillaLoc, BugzillaAbl, BugzillaGen to the appropriate file (which, I'm
> guessing, is global/variables.none.tmpl or some other file in global/) to
> make them available to the Bugzilla installation that will be employed. As
> Turkish has these two issues I've mentioned above, I can not translate
> these noun forms seperately nor can I correctly use in my translations
> suffixes like 'nin, 'nın, 'da, 'de .. without knowing the value of
> terms.Bugzilla. So in its current form, it is not possible to have an
> optimum Turkish translation of Bugzilla.

Yes you should put the whole paradigm of terms.Bugzilla into 
global/variables.none.tmpl, as it is done for terms.bug in many languages. 
Include possessive case also (like terms.Bugzilla_nin to keep text more 
readable). Then you use correct form within templates.  Customizers willing to 
rename Bugzilla should also change the paradigm accordingly.

> On to the questions:
> Is it possible that the mentioned variables be added to Bugzilla code (3.2
> if possible)?
> If so, if these variables are put into global/*whatever*, will/can they be
> backported to 3.2 or 3.2.1, or will/can they be included in 3.4 and later?

These variables are used only by template/tr/* so having them in 
template/tr/default/global/variables.none.tmpl is sufficient.  English templates 
do not need these, and other languages already have different sets.

Good point: until you translate 100% of your templates, you may want to keep 
terms.bug as 'bug' and use (for example) terms.bug_nom for Turkish term.  This 
way you will avoid ugly renderings where English messages refer to localized terms.

> Questions/ comments/ requests welcome. This is sort of a cross-posting (also
> reported as a bug in Bugzilla's Bugzilla) but I needed clarification and
> this list probably has a larger user-base.

   Regards,
   Vitaly.
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla