On 12/14/2014 11:07 AM, Sophie wrote:
...
And I have yet to see those technical marvels we've been promised will
compensate for this problem (promised with lot of eff-ing at silly
localisers, by the way).
Hey, those scripts are done by people to help us, so don't shout on
them. We will discuss
On 12/14/2014 12:47 PM, Khaled Hosny wrote:
I have been localising software for much longer
than I have been making fonts (or even writing
software) and I know that reviewing a few
hundred strings that were trivially changed is
not the end of the world. Usually the tool I'm
using (be it Pootle
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
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
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
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
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
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
