Not so feasible, I think.
Work based on another translation would very
likely mean missing important nuances.
Ironically, this was the case with English (!)
in times of OO 2.0, when it was somewhat more
instructive to look into German strings
(originating from StarOffice) for the precise
me
Those changes, while possibly worthwhile from
en_US perspective, are not related to what
localised interface looks like. Since version 2
the workload in ui strings might easily
constitute +100% of initial 25k. Did the ui
change that much? No.
Yury
On 12/13/2014 03:22 AM, Khaled Hosny wrote:
True but what gets my goat is that many of these are *totally*
arbitrary. Case in point, sentence case vs title case. Unfortunately
this debate comes at a time when Microsoft has gone *exactly* 180° the
other way (going forward) compared to LibreOffice. So that makes it
arbitrary.
That's even
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”, really
scary. I can understand people being annoyin
Sgrìobh Christian Lohmaier na leanas 12/12/2014 aig 20:42:
And all those *##* who keep ranting about the changing caps and
similar: It has been made pretty clear already that any such change
would be handled automatically with no need for retranslating. Shut
the f* up/write your stuff in other t
12.12.2014. u 21:42, Christian Lohmaier je napisao/la:
In other words: If you don't want to use master: Don't use master.
Changes you do on master will be overridden when you request copying
from 4-4. So either do any merges yourself, or don't complain
afterwards. ciao Christian
Since I did
I believe the strings can be found by everybody using a search in the
Comments field for the codes given below. Check "Comments" and "Exact
match" when searching. The search is very fast when Exact match is checked.
But yes, it would be easier if everybody just had access to the greek
translation
Hi Stanislav, *,
On Thu, Dec 11, 2014 at 6:01 PM, Stanislav Horáček
wrote:
>
> the new workflow is a bit unclear for me. If I work only in branches, let's
> say in 4.5, does it mean that
> - changes from 4.5 branch will be ported back to master (if so, when?),
No. Nothing will be merged to maste
12.12.2014 u 16:00, Sérgio Marques je napisao/la:
Because you should be against something upfront. If it doesn't affect your
current workflow, why do you care?
I care because I still didn´t understood how the merge between branches
will be. So, for that reason, I´m still unsure if it will affe
2014-12-12 14:11 GMT+00:00 Mihovil Stanic :
>
>
> 12.12.2014 u 15:04, Sérgio Marques je napisao/la:
>
>> So why the hell someone decided to ignore what I and others told her?
>>
>
> Because you should be against something upfront. If it doesn't affect your
> current workflow, why do you care?
>
I
12.12.2014 u 15:04, Sérgio Marques je napisao/la:
So why the hell someone decided to ignore what I and others told her?
Because you should be against something upfront. If it doesn't affect
your current workflow, why do you care?
As I understood it, you will have option to use it or not use
2014-12-12 11:45 GMT+00:00 Stanislav Horáček :
>
> Dne 12.12.2014 v 11:54 Olivier Hallot napsal(a):
>
>>
>>
>> On 12/12/2014 08:18, Sérgio Marques wrote:
>>
>>> Sorry, I don't get it. Now: 4.4 was created and translations from 4.3
> appeared there.
> Future: Which translations will app
2014-12-12 11:56 GMT+00:00 Mihovil Stanic :
>
>
> 12.12.2014 u 12:45, Stanislav Horáček je napisao/la:
>
>>
>> This workflow means that everyone is forced to work on master - otherwise
>> it is needed to translate the same strings again and again in branches
>> which makes no sense.
>>
>> And that'
Then what on earth do we gain by this 'new' approach? Is the idea that
some very active locales like German will spot problems on master fast
and maybe raise the issue before it hits stable strings?
Michael
Sgrìobh Mihovil Stanic na leanas 12/12/2014 aig 11:58:
12.12.2014 u 12:53, Michael Ba
12.12.2014 u 12:53, Michael Bauer je napisao/la:
- minimize retranslation work by not presenting localizer with
hundreds of retranslations when the English source goes from a
formatted something to an unformatted something or back again?
No. But you will see it before anyone else. :)
- pre
12.12.2014 u 12:45, Stanislav Horáček je napisao/la:
This workflow means that everyone is forced to work on master -
otherwise it is needed to translate the same strings again and again
in branches which makes no sense.
And that's why I am confused - because we were assured that it will be
Could someone please explain what's currently proposed in terms that
avoid terms like 'master' There are a lot of localizers who work on the
basis of 'I see a string, I translate it' who aren't necessarily
familiar with masters and branches and whatnots but since this will
affect localizers, th
Dne 12.12.2014 v 11:54 Olivier Hallot napsal(a):
On 12/12/2014 08:18, Sérgio Marques wrote:
Sorry, I don't get it. Now: 4.4 was created and translations from 4.3
appeared there.
Future: Which translations will appear in 4.5 when it is created - from
4.4 or from master? Translations of the sam
That's great, people which use master for translation will be our canary
birds!
If devs start changing caps, ', ... etc, please warn us so we can spam
them. :)
12.12.2014 u 11:54, Olivier Hallot je napisao/la:
On 12/12/2014 08:18, Sérgio Marques wrote:
Sorry, I don't get it. Now: 4.4 was cr
On 12/12/2014 08:18, Sérgio Marques wrote:
>> Sorry, I don't get it. Now: 4.4 was created and translations from 4.3
>> > appeared there.
>> > Future: Which translations will appear in 4.5 when it is created - from
>> > 4.4 or from master? Translations of the same strings can differ between
>> > t
2014-12-11 19:28 GMT+00:00 Stanislav Horáček :
>
> Dne 11.12.2014 v 18:44 Sophie napsal(a):
>
>> Le 11/12/2014 18:01, Stanislav Horáček a écrit :
>>
>>> Hi,
>>>
>>> So Cloph will create a master project for all the languages. You can
choose where you want to translate, on master or on the nex
21 matches
Mail list logo
