Hi all,
2015-01-27 2:17 GMT+03:00 Harald Köster harald.koes...@mail.de:
Hi all,
some menu items are not translated into German in version 4.4.0.3.
According Christian Kühl all items are translated in Pootle, hence it
seems that these items are not marked as translatable.
The following
Hi Jan,
2015.01.26 16:43, Jan Holesovsky rašė:
Mihovil Stanić píše v Po 26. 01. 2015 v 10:25 +0100:
Cosmetic changes (~ to _ or Status to Status: or ... to … or those
different quote styles I don't even have on my keyboard) and anything
similliar - NOT OK if you don't script it for all
Hi Rimas, all
Le 27 janv. 2015 19:32, Rimas Kudelis r...@akl.lt a écrit :
Hi Jan,
2015.01.26 16:43, Jan Holesovsky rašė:
Mihovil Stanić píše v Po 26. 01. 2015 v 10:25 +0100:
Cosmetic changes (~ to _ or Status to Status: or ... to … or those
different quote styles I don't even have on
Hi!
Am 27.01.2015 um 08:39 schrieb Mihovil Stanić:
1, 3 and 4 are not translated for me also (4.4.0.3 HR locale), but 2 is.
2nd I can confirm was a translation issue, I corrected it now.
27.01.2015 u 00:17, Harald Köster je napisao/la:
Hi all,
some menu items are not translated into
Hi,
in this bug report:
https://bugs.documentfoundation.org/show_bug.cgi?id=68247
during discussion we came to a proposal to change default Fontwork
text in Fontword samples to something more l10n acceptable, i.e.
Abc123 or LibreOffice.
Current implementation would require a lot of coding to
On Tue, Jan 27, 2015 at 5:43 PM, Wols Lists antli...@youngman.org.uk wrote:
Am I right in reading into this, that master is using American English?
And if so, why? Seeing as LibreOffice is, at heart, a European program
surely it should be using English?
Like British English? RP? Let's be
2015-01-28 2:59 GMT+01:00 Robinson Tryon bishop.robin...@gmail.com:
2) What will the language be for builds w/o langpacks? Just a generic
'English'? (maybe we can call it LibreOffice English :-)
Maybe there should be no such build at all.
--
To unsubscribe e-mail to:
2015-01-27 16:09 GMT+01:00 Michael Bauer f...@akerbeltz.org:
PS the current setup is not foolproof either as we sometimes get really
bad strings, linguistically bad that is.
If this is such a concern, then why don't we set up a panel of experiences
localizers who are willing to help
Hi Jesper,
Jesper Hertel píše v Út 27. 01. 2015 v 14:08 +0100:
That's why we were thinking of a en_US version as a real
language and
different from the sources and
But at some stage this will have to apply to the sources
Why?
Because the
PS the current setup is not foolproof either as we sometimes get really
bad strings, linguistically bad that is.
If this is such a concern, then why don't we set up a panel of
experiences localizers who are willing to help developers judge if a
change is semantic or cosmetic before we land
A person who cannot decide if a string change is semantic or cosmetic to
en-US should not be messing around with the string names in the first
place, if you ask me.
Ok so maybe occasionally they might get it wrong. That still produces a
lot LESS workload to fix that landing 2000 cosmetic
hi.
i cannot type in translation forms in translation site.
can you give me right to translate to tatar language? my username is qdb.
i have written to tatar team lead email, several days ago, but there
was not response.
--
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Hi :)
A big
+1
from me! I guess there might be teething problems but hopefully we
can all be patient with those and just enjoy the advantages of the new
system more and more :)
Many thanks and regards from
Tom :)
On 25 January 2015 at 09:22, Florian Effenberger
flo...@documentfoundation.org
Hi :)
I'm not sure about the idea of the panel of experienced localisers.
That just seems like even more work for those localisers and i think
Sophie is aiming to reduce everyone's work-load through this thread.
Sophie seems to be aiming to solve this whole problem once and for
all so that it
Hi Sophie,
Le 19/01/2015 10:54, Sophie a écrit :
Hi all,
For information, Cloph and me will meet with Dwayne (Pootle developer)
at Fosdem. We will discuss (and hopefully be able to solve) the
performance issue and the update to new version. I'll give you feedback
on this meeting and the
Hi Dinar,
Tatar has been really quiet, since 2013 so I have given you almost all
rights. Certainly enough to translate. Let us know if the current team
lead is not responding at all?
Happy translating
Michael
Sgrìobh dinar qurbanov na leanas 27/01/2015 aig 10:33:
hi.
i cannot type in
2015-01-26 16:40 GMT+01:00 Jan Holesovsky ke...@collabora.com:
That's why we were thinking of a en_US version as a real language and
different from the sources and
But at some stage this will have to apply to the sources
Why?
--
To unsubscribe e-mail to:
Hi,
2015.01.26 17:40, Jan Holesovsky rašė:
Sophie píše v Po 26. 01. 2015 v 16:19 +0100:
That's why we were thinking of a en_US version as a real language and
different from the sources and
But at some stage this will have to apply to the sources - and at that
time, it will be even worse
2015-01-28 2:59 GMT+01:00 Robinson Tryon bishop.robin...@gmail.com:
1) will inconsistency of nouns (e.g. color vs. colour), inconsistency
of grammar, etc.. within the sources in master make translation harder
for the native-lang teams?
Not if they use Pootle and set up additional language
2015-01-28 2:59 GMT+01:00 Robinson Tryon bishop.robin...@gmail.com:
3) Who's going to step up to maintain en_US? (I'd love to help, but
I'm working tons of hours as it is)
There must be some American users of LibreOffice? Wouldn't en_US just be
like any other language, with the same challenge
20 matches
Mail list logo
