[mythtv] [mythtv-commits] Ticket #7475: [PATCH] Trivial, Ok->OK nit in mythfrontend
robert.mcnamara at gmail.com
Sun Nov 1 20:25:45 UTC 2009
On Sun, Nov 1, 2009 at 1:18 PM, Nicolas Riendeau <knight at teksavvy.com> wrote:
> robertm wrote:
>> Translations needing updates is not a valid reason to keep incorrect
>> language/terminology. Discussion belongs on lists.
> If we submit a patch that breaks the translation files for something as
> trivial as a case change (or a typo) should we submit a patch for the
> translation files as well (personally I would be tempted to do so).
> I'm asking that question because I noticed when I worked on the patch I
> submitted in ticket 7473 (http://svn.mythtv.org/trac/ticket/7473) that there
> are places where British English (favourites) is used instead of American
> English (favorites) AFAIK** when the rest of the application seems to use
> American English. There are also a few places where I or friends noticed
> I did not submit a patch to the translation files in ticket 7473 because the
> string was not initially translatable but I know there are other places
> where favourites is used (and there are also place when favorites is
> Thank you,
> ** English is not my mother tongue so I could be wrong
Well, Reynaldo is working on many aspects of our translation stuff,
including imrpoving the method by which we generate translation
files-- there are always going to be numerous strings that get
changed/added/removed. If I was forced to write numerous
translations/etc. every time I fixed a string/changed a string/wrote a
new string, I would never get anything done. IMO the change doesn't
"break" translations, it just renders the current ones out of date.
And that's why we have translators/why we send out a call for
translations a month or two before release. :)
PS-- I think your mythgame patch is right-- we tend to err on the side
of American english, but the string should definitely be translatable.
More information about the mythtv-dev