On 21/10/17 23:44, jonathon wrote:
> On 10/21/2017 09:16 PM, Wols Lists wrote:
>
>> I think you mean users of the Scots language. Not to be confused with the
>> language of the Scots.
>
> There is a dialect of English called Scottish English. It is a
> combination of Gaelic and English.
And wh
On 10/21/2017 09:16 PM, Wols Lists wrote:
> I think you mean users of the Scots language. Not to be confused with the
> language of the Scots.
There is a dialect of English called Scottish English. It is a
combination of Gaelic and English.
> Sassenachs - ie Angles - speak Scots. Scots speak G
On 20/10/17 19:25, jonathon wrote:
> If users of African American Vernacular English want to create that
> L10N, more power to them. Likewise, if users of Scottish English want
> to create an L10N, let Bobby lede the way.
I think you mean users of the Scots language. Not to be confused with
the l
On 10/20/2017 03:54 PM, Wols Lists wrote:
> and en_US are actually two distinct languages with different vocabularies and
> spellings (and indeed, maybe grammars?).
FWIW, _African-American Vernacular English_ utilizes a tense that is not
present in either _Standard American English_ nor _Receive
On 17/10/17 15:51, Toki wrote:
> On 10/15/2017 10:44 AM, Adolfo Jayme Barrientos wrote:
>> > Why is it only obvious to me that creating a separate “English locale”
>> > (IOW, a complete copy of the source strings which would have to be kept in
>> > sync and coherent at all times) is not sustainable
On 10/15/2017 10:44 AM, Adolfo Jayme Barrientos wrote:
> Why is it only obvious to me that creating a separate “English locale”
> (IOW, a complete copy of the source strings which would have to be kept in
> sync and coherent at all times) is not sustainable?
The _ONLY_ issue with having both Engli
Le 16/10/2017 à 14:22, Kaganski Mike a écrit :
> On 10/16/2017 3:16 PM, Sophie wrote:
>> Hi Mike,
>>
>> Le 13/10/2017 à 23:31, Kaganski Mike a écrit :
>>> Hello!
>>>
>>> Recently I was approached by members of our local community who manage
>>> the translation of LibreOffice UI to Russian. I was to
On 10/17/2017 09:17 AM, Jan Iversen wrote:
> I have never understood why we make English a special case, and assume all
> developers are perfect English speakers.
Two reasons:
* Inertia;
* An unwillingness to create both English(US) and English(UK) as
independent l10n projects.
That every profe
Hi,
On 10/17/2017 2:39 PM, Eike Rathke wrote:
> Hi Mike,
>
> On Sunday, 2017-10-15 10:55:17 +, Kaganski Mike wrote:
>
>> The source string is the key for all translations, and is kept immutable
>> after creation. But the localization string might change later, e.g. to
>> be consistent, like
Hi Mike,
On Monday, 2017-10-16 12:16:01 +, Kaganski Mike wrote:
> On 10/16/2017 10:08 AM, David Tardon wrote:
> > On Fri, Oct 13, 2017 at 09:31:41PM +, Kaganski Mike wrote:
> >> 3. Any change in English translation (not in immutable source strings!)
> >> would trigger all other translatio
Hi Mike,
On Sunday, 2017-10-15 10:55:17 +, Kaganski Mike wrote:
> The source string is the key for all translations, and is kept immutable
> after creation. But the localization string might change later, e.g. to
> be consistent, like this:
>
> source locale
> "do foo acti
Hi
Actually many international projects, do not use english strings in the source
as such, they use identifiers. All project I know of, have let the developer
enter a suggested string, which is then through tooling converted to an
identifier, and the suggestion is moved to pootle.
Please reme
On 10/15/2017 1:44 PM, Adolfo Jayme Barrientos wrote:
> Why is it only obvious to me that creating a separate “English locale”
> (IOW, a complete copy of the source strings which would have to be kept
> in sync and coherent at all times) is not sustainable?
Why kept coherent all times? Initially
On 10/16/2017 10:08 AM, David Tardon wrote:
> On Fri, Oct 13, 2017 at 09:31:41PM +, Kaganski Mike wrote:
>> 3. Any change in English translation (not in immutable source strings!)
>> would trigger all other translations of this string to become fuzzy
>> (thus not loosing previous translation, b
On 10/16/2017 3:16 PM, Sophie wrote:
> Hi Mike,
>
> Le 13/10/2017 à 23:31, Kaganski Mike a écrit :
>> Hello!
>>
>> Recently I was approached by members of our local community who manage
>> the translation of LibreOffice UI to Russian. I was told that they have
>> a regularly recurring problem, tha
Hi Mike,
Le 13/10/2017 à 23:31, Kaganski Mike a écrit :
> Hello!
>
> Recently I was approached by members of our local community who manage
> the translation of LibreOffice UI to Russian. I was told that they have
> a regularly recurring problem, that each time a developer changes an
> English
Hi,
On Fri, Oct 13, 2017 at 09:31:41PM +, Kaganski Mike wrote:
> 3. Any change in English translation (not in immutable source strings!)
> would trigger all other translations of this string to become fuzzy
> (thus not loosing previous translation, but just signaling the
> requirement to re
Why is it only obvious to me that creating a separate “English locale”
(IOW, a complete copy of the source strings which would have to be kept in
sync and coherent at all times) is not sustainable?
Fix Pootle. Or let’s have Weblate.
___
LibreOffice maili
Hello!
Recently I was approached by members of our local community who manage
the translation of LibreOffice UI to Russian. I was told that they have
a regularly recurring problem, that each time a developer changes an
English string in LibreOffice UI, they have that string untranslated in
poo
19 matches
Mail list logo
