Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Akerbeltz.org
I like Oliver's idea. That way, en-US can change its caps, commas, typos, formatted vs non-formatted typography on a daily basis to their heart's content without kicking the rest of the planet into the neolithic, l10n-wise. If I may point out the commercial angle on this - I charge $35 an hour fo

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Olivier Hallot
On 30/11/2014 14:11, Mihovil Stanic wrote: > > 30.11.2014. u 9:10, Andras Timar je napisao/la: Program UI isn't a typography showcase. >>> Of course it is! We’re building an office suite, remember? An office >>> suite which has to do with typography a great lot. And even if it >>> didn’t, i

Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Rimas Kudelis
Hi, 2014.11.30 16:23, Christian Lohmaier wrote: >>> I agree this will be annoying, because at the very least, the localizers >>> will have to re-approve a lot of their old translations when these >>> changes land. At least in the case of "don't" though, maybe this change >>> could be automated, if

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Mihovil Stanic
30.11.2014. u 9:10, Andras Timar je napisao/la: Program UI isn't a typography showcase. Of course it is! We’re building an office suite, remember? An office suite which has to do with typography a great lot. And even if it didn’t, it’s supposed to demostrate a level of polish and leave a better

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Yury Tarasievich
On 11/30/2014 02:33 PM, Jesper Hertel wrote: Just because you do not like an idea or are afraid of its consequences there is no reason to shoot it down with sarcasm or other violent methods. That is never helpful. Oh dear. What to do then, if one doesn't like the idea and does NOT in fact hav

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Christian Lohmaier
Hi Yury, *, On Sun, Nov 30, 2014 at 10:07 AM, Yury Tarasievich wrote: > > Well, as Adolfo tells us, it's "bah" to Windows users". However, Linux's > en_US keymap (which I'm using right now) also does not have any of mentioned > glyphs on the compose key. Compose sequences should be the same rega

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Jesper Hertel
2014-11-30 13:01 GMT+01:00 Martin Srebotnjak : > Hi, Jesper, > > in LO Pootle 135 translation teams are stated. If we take out about 20 > teams with really scarce tranlations, that means 115 teams. > > 5 changed strings in English UI x 115 = 575 changed strings in > localization po files to re-tra

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Martin Srebotnjak
Hi, Jesper, in LO Pootle 135 translation teams are stated. If we take out about 20 teams with really scarce tranlations, that means 115 teams. 5 changed strings in English UI x 115 = 575 changed strings in localization po files to re-translate 115 people being affected by this change. I am not a

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Jesper Hertel
Please, guys, those of you who want to fight, could you please step outside and do that, so the rest of us can work? Just because you do not like an idea or are afraid of its consequences there is no reason to shoot it down with sarcasm or other violent methods. That is never helpful. If you have

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Yury Tarasievich
On 11/30/2014 12:07 PM, Yury Tarasievich wrote: ... What's strictly "incorrect" in straight apostrophe, anyway? ... Anyway, here's an idea for you guys about to suffer from this: diff the en_US source before and after apostrophe nice-fication, then create a program which looks at the apostro

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Martin Srebotnjak
For those purposes a fork of LibreOffice would be viable, named PureOffice. But there would probably be no 100 % localizations provided for it. Lp, m. 2014-11-30 8:30 GMT+01:00 Adolfo Jayme Barrientos : > 2014-11-29 23:38 GMT-06:00 Yury Tarasievich said: > > Said recommendations, while formaly c

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Yury Tarasievich
On 11/30/2014 11:23 AM, Rimas Kudelis wrote: 2014.11.30 07:38, Yury Tarasievich rašė: ... And if you use Windows and want to make inputting these characters even more convenient, you can always customize your keyboard layout adding missing typographical symbols to the AltGr (or any other) lay

Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Rimas Kudelis
2014.11.30 07:38, Yury Tarasievich rašė: > On 11/30/2014 05:13 AM, Adolfo Jayme Barrientos wrote: > ... >> In case you guys didn’t know, Apple [1], Microsoft [2] and GNOME [3] >> are all recommending the use of typographical apostrophes and >> quotation marks, among other characters that have been

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-30 Thread Andras Timar
On Sun, Nov 30, 2014 at 8:30 AM, Adolfo Jayme Barrientos wrote: > 2014-11-29 23:38 GMT-06:00 Yury Tarasievich said: >> Said recommendations, while formaly correct, are subverted by the fact that >> there are no commonly accessible methods to keyboard-input all those "fancy" >> glyphs. > > Wrong. >

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-29 Thread Adolfo Jayme Barrientos
2014-11-29 23:38 GMT-06:00 Yury Tarasievich said: > Said recommendations, while formaly correct, are subverted by the fact that > there are no commonly accessible methods to keyboard-input all those "fancy" > glyphs. Wrong. OS X and Linux distros include punctuation (which is not “fancy” at all)

[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't

2014-11-29 Thread Yury Tarasievich
On 11/30/2014 05:13 AM, Adolfo Jayme Barrientos wrote: ... In case you guys didn’t know, Apple [1], Microsoft [2] and GNOME [3] are all recommending the use of typographical apostrophes and quotation marks, among other characters that have been historically ... Said recommendations, while form