Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread Mihovil Stanic
I would really like to see what kind spelling rules in en_US supports this: https://translations.documentfoundation.org/fr/libo_ui/translate/sc/uiconfig/scalc/ui.po#unit=79290454 Read filter criteria from --> Read Filter Criteria From If this isn't purely cosmetical change, I don't know what it i

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread Tom Davies
Hi :) Earlier there was a suggestion of creating some sort of buffer-language between English (US) and all the other languages. Is there a language that doesn't have so many 'little' changes that affect so much? One that gets all the translations done really fast? Perhaps Spanish, Portugese (Br)

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread Adolfo Jayme Barrientos
2014-12-12 18:22 GMT-06:00 Khaled Hosny : > On Fri, Dec 12, 2014 at 10:00:45PM +, Michael Bauer wrote: >> the nonsense around cosmetic changes to en-US > > As a localiser, I find it worrying that “localisers” think that using > correct capitalisation or punctuation marks “nonsense cosmetics”, r

Re: [libreoffice-l10n] Cosmetic changes?

2014-12-13 Thread jonathon
On 13/12/14 00:22, Khaled Hosny wrote: > As a localiser, I find it worrying that “localisers” think that using > correct capitalisation or punctuation marks “nonsense cosmetics”, really > scary. Changes made in one dialect of one language should neither affect, nor effect changes in other dial

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread jonathon
On 13/12/14 05:35, Tom Davies wrote: > If so might that be a better language to use as the base-line to translate > from? Not a language, but a working assumption that all supported languages are translations of the strings from the source UI. IOW, you have an en_US team, alongside an en_UK t

Re: [libreoffice-l10n] Cosmetic changes?

2014-12-13 Thread Khaled Hosny
On Sat, Dec 13, 2014 at 07:42:41PM +, jonathon wrote: > > > On 13/12/14 00:22, Khaled Hosny wrote: > > > As a localiser, I find it worrying that “localisers” think that using > > correct capitalisation or punctuation marks “nonsense cosmetics”, really > > scary. > > Changes made in one dia

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread Khaled Hosny
On Sat, Dec 13, 2014 at 09:41:57AM +0100, Mihovil Stanic wrote: > I would really like to see what kind spelling rules in en_US supports this: > https://translations.documentfoundation.org/fr/libo_ui/translate/sc/uiconfig/scalc/ui.po#unit=79290454 > Read filter criteria from --> Read Filter Criteria

Re: [libreoffice-l10n] Cosmetic changes?

2014-12-13 Thread Michael Bauer
Khaled, That is precisely the point. Most locales are more specific with regards to things like sentence case vs camel case. English just changes its approach to this issue depending on the phase of the moon and the number of ripe mangos in Florida. In German, you can't just decide that sudde

Re: [libreoffice-l10n] Cosmetic changes?

2014-12-13 Thread Mihovil Stanic
Exactly, you wrapped it nicely. In croatian it's similiar, only names (people, brands, companies...) and some nouns can have capital letter, rest can't. I'm not really sure if english doesn't have any caps rules or people just ignore them for "style" sake. From my point of view new All Caps W

Re: [libreoffice-l10n] Cosmetic changes?

2014-12-13 Thread jonathon
On 13/12/14 21:45, Khaled Hosny wrote: >> Changes made in one dialect of one language should neither affect, nor >> effect changes in other dialects of the same language, much less other >> languages. > > Huh? English (US) is the “source” language, Treating en_US, en_DE, en_UK, or any variant t

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread jonathon
On 13/12/14 21:52, Khaled Hosny wrote: > So, the original strings were badly written, That is just one of myriad reasons why treating en_US, en_DE, en_UK, or any variant thereof as the "source" language is, at best, translation mismanagement. > specific (unless your language does not use punctu

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread Khaled Hosny
On Dec 14, 2014 3:07 AM, "jonathon" wrote: > > On 13/12/14 21:52, Khaled Hosny wrote: > > > So, the original strings were badly written, > > That is just one of myriad reasons why treating en_US, en_DE, en_UK, or > any variant thereof as the "source" language is, at best, translation > mismanageme

Re: [libreoffice-l10n] Cosmetic changes?

2014-12-13 Thread Khaled Hosny
I don't understand why people are fixated on the case changes! These are not the only “cosmetic” changes people were complaining about. The changes themselves were never may point, but the way people is complaining about them is what I'm worried about as it shows that some localiser seem to have to

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread Yury Tarasievich
On 12/14/2014 09:19 AM, Khaled Hosny wrote: ... But that was not my point, I was complaining about people who think that consistency, following linguistic rules and proper typography are usless cosmetics. Regardless of how localisation will be done or what language is ... Then you completely mi

Re: [libreoffice-l10n] Cosmetic changes? (was Workflow based on master)

2014-12-13 Thread jonathon
On 14/12/14 06:19, Khaled Hosny wrote: > So, what translators are supposed to translate then? Whatever is in that source. That language, with whatever spelling, grammatical, semantic markup, and presentation markup it includes, is what everybody uses. If you want an en_US localization, then you