2014-12-01 20:38 GMT+02:00 Rimas Kudelis :
> > It would for example also be possible to have "master" project in
> > pootle (instead of just for the release-branches), so that the amount
> > of changes are incremental, and not all one or two months before a new
> > major release.
> > (but that of
Hi Christian,
2014.12.01 00:32, Christian Lohmaier wrote:
> On Sun, Nov 30, 2014 at 10:16 PM, Olivier Hallot
> wrote:
>> On 30/11/2014 18:52, Rimas Kudelis wrote:
>>> 2014.11.30 19:13, Olivier Hallot wrote:
>> painless migration was my hope when I raised the issue, but saddly it
>> didn't show up
On 12/01/2014 01:11 PM, Christian Lohmaier wrote:
On Mon, Dec 1, 2014 at 5:58 AM, Yury Tarasievich
wrote:
On 11/30/2014 11:52 PM, Rimas Kudelis wrote:
And why is not anyone (besides me) discussing automation, of that same
problem, too?
Probably because there is nothing to discuss as it has a
Hi all,
Le 30/11/2014 23:32, Christian Lohmaier a écrit :
> Hi Olivier, *,
>
> On Sun, Nov 30, 2014 at 10:16 PM, Olivier Hallot
> wrote:
>> On 30/11/2014 18:52, Rimas Kudelis wrote:
>>> 2014.11.30 19:13, Olivier Hallot wrote:
>>
>> painless migration was my hope when I raised the issue, but saddl
On Mon, Dec 1, 2014 at 5:58 AM, Yury Tarasievich
wrote:
> On 11/30/2014 11:52 PM, Rimas Kudelis wrote:
>
> And why is not anyone (besides me) discussing automation, of that same
> problem, too?
Probably because there is nothing to discuss as it has already been
explained that it can be done/to wh
On 11/30/2014 11:52 PM, Rimas Kudelis wrote:
...
I don't really think this would be viable solution in the long run.
Somebody would have to maintain that "translation" for years just
because in 2014 localizers made a fuss out of a one-time problem that
could (and should) have been automated not t
Hi Olivier, *,
On Sun, Nov 30, 2014 at 10:16 PM, Olivier Hallot
wrote:
> On 30/11/2014 18:52, Rimas Kudelis wrote:
>> 2014.11.30 19:13, Olivier Hallot wrote:
>
> painless migration was my hope when I raised the issue, but saddly it
> didn't show up in time. Such Changes In Capital Letters And Sem
Hi Rimas
On 30/11/2014 18:52, Rimas Kudelis wrote:
> Hi,
>
> 2014.11.30 19:13, Olivier Hallot wrote:
>> Lets invent a new language in the world named Liboish - LibreOffice
>> language - that in fact is often confused with en_US, but it is not the
>> same.
>>
>> I suggest to create a new entry in
Hi,
2014.11.30 19:13, Olivier Hallot wrote:
> Lets invent a new language in the world named Liboish - LibreOffice
> language - that in fact is often confused with en_US, but it is not the
> same.
>
> I suggest to create a new entry in Pootle, named en-US so that we get a
> translation from Liboish
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
On 30/11/14 12:58, Jesper Hertel wrote:
> But how come we would have to retranslate?
It shows up as "untranslated", and the only way to change the status is
to retranslate it, even if that retranslation is nothing more than a
mouse click approving the existing translation.
> to find a solution t
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
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
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
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
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
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
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
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
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
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
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
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
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.
>
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)
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
2014-11-29 15:05 GMT-06:00 Mihkel Tõnnov said
> Typographically speaking, ’ *is* the correct character. The use of
> so-called straight or typewriter apostrophes (and quotes) in computing is
> basically restricting oneself to a limitation that is no longer justified
> in Unicode-age. So in my view,
Hi Jesper, *,
Typographically speaking, ’ *is* the correct character. The use of
so-called straight or typewriter apostrophes (and quotes) in computing is
basically restricting oneself to a limitation that is no longer justified
in Unicode-age. So in my view, the changing should ultimately go the
28 matches
Mail list logo
