Hi,
I agree with Sophie on this, some kind of overall check.
Since there are tools like LanguageTool maybe there is a way to automatize
this:
1) set a local LT server
2) serve all LO strings with identifiers for later reference without the
XML and other tags to LT server and log all errors report
Hi Andras,
Le 05/12/2013 11:42, Andras Timar a écrit :
> On Thu, Dec 5, 2013 at 10:52 AM, Robinson Tryon
> wrote:
>> On Thu, Dec 5, 2013 at 4:37 AM, Mateusz Zasuwik wrote:
>>> 2013/12/2 Sophie
>>>
>>> And en-US team need glossary, surely. I see many inconsistent phrases like
>>> "*Please conside
On Thu, Dec 5, 2013 at 10:52 AM, Robinson Tryon
wrote:
> On Thu, Dec 5, 2013 at 4:37 AM, Mateusz Zasuwik wrote:
>> 2013/12/2 Sophie
>>
>> And en-US team need glossary, surely. I see many inconsistent phrases like
>> "*Please consider restart LibreOffice* to set new features".
>
> S..what's t
On Thu, Dec 5, 2013 at 4:37 AM, Mateusz Zasuwik wrote:
> 2013/12/2 Sophie
>
> And en-US team need glossary, surely. I see many inconsistent phrases like
> "*Please consider restart LibreOffice* to set new features".
S..what's the best way for me to identify and squash bugs in
strings like th
2013/12/2 Sophie
> Hi Mirosław,
> Le 02/12/2013 18:37, Mirosław Zalewski a écrit :
> > Why do I say that? Because these are the reasons that makes
> > me not believe in success of this initiative. Translating LibreOffice
> > was ungrateful in the past and I think that this time it will not only
>
On Mon, Dec 2, 2013 at 7:03 PM, Sophie wrote:
> > Also, Polish translation is periodically changed without our knowledge
> > and consent. Last time I remember someone has superseded all "Liczba"
> > with "Ilość" (first one is for countable, second for uncountable; it's
> > like changing "many" to
Sophie wrote:
>> a) Can somebody layout precisely what an en_US l10n team/group/individual
>> would do?
>as, I said, I think the first thing is to have an up to date glossary, then
>check for the consistency in the menus/dialogs/tabs, check for the
Camel case use, check that the good terms
On Mon, Dec 2, 2013 at 2:37 PM, Sophie wrote:
>>
>> a) Can somebody layout precisely what an en_US l10n
>> team/group/individual would do?
>
> as, I said, I think the first thing is to have an up to date glossary,
> then check for the consistency in the menus/dialogs/tabs, check for the
> Camel ca
Hi Jonathon,
Le 02/12/2013 20:22, tk a écrit :
>
>
> Robinson Tryon wrote:
>
>>> the one responsible of the en_US version. And I don't think
>>> somebody
> is in fact.
>
>> Hmm. Sophie - should we consider spinning-up a community for
>> en_US? I'm not sure I have much time to spend on it right
Robinson Tryon wrote:
>> the one responsible of the en_US version. And I don't think somebody
is in fact.
>Hmm. Sophie - should we consider spinning-up a community for en_US?
>I'm not sure I have much time to spend on it right now, but I could
a) Can somebody layout precisely what an en_US l10
On Mon, Dec 2, 2013 at 1:03 PM, Sophie wrote:
>>> Although the origin of the english strings are from the developers,
>>> and they are focused in producing code and fixing bugs more than
>>> writing beautiful english, it may be necessary that we - the
>>> community and in a continuous process - st
Hi Mirosław,
Le 02/12/2013 18:37, Mirosław Zalewski a écrit :
> Dnia 2013-12-02, o godz. 09:39:49
> Olivier Hallot napisał(a):
>
>> Although the origin of the english strings are from the developers,
>> and they are focused in producing code and fixing bugs more than
>> writing beautiful english,
Dnia 2013-12-02, o godz. 09:39:49
Olivier Hallot napisał(a):
> Although the origin of the english strings are from the developers,
> and they are focused in producing code and fixing bugs more than
> writing beautiful english, it may be necessary that we - the
> community and in a continuous proc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Olivier,
Le 02/12/2013 14:04, Olivier Hallot a écrit :
> Hi Sophie,
>
> Em 02-12-2013 10:21, Sophie escreveu:
>> I thought that Glade would bring more quality but what is missing
>> the most is maybe a referential glossary for developers (or they
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sophie,
Em 02-12-2013 10:21, Sophie escreveu:
> I thought that Glade would bring more quality but what is missing the
> most is maybe a referential glossary for developers (or they have one
> that should be updated maybe).
Although a good idea in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 02/12/2013 12:39, Olivier Hallot a écrit :
> Hello
>
> As translator for LibreOffice since 2003, I often see less than
> optimal english strings to translate and I believe other
> translators also has the perception that the original english can
>
Hi :)
+1
It certainly seems that way. However it also seems that the number of
troublesome strings is remarkably small. People do sometimes post
such strings to this list and various people are here ready to discuss
what they think it means. Although some it it might look quite rough
it seems to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
As translator for LibreOffice since 2003, I often see less than optimal
english strings to translate and I believe other translators also has
the perception that the original english can be improved (other than typos).
Although the origin of th
18 matches
Mail list logo
