2012/1/3 Sérgio Marques
>
>
> 2011/12/31 Andras Timar
>
>> 2011/12/31 Andras Timar :
>> >
>> > As for the Insert Rows/Columns modal dialog, it was a good catch that
>> > needs to be fixed. But if it have been good enough for the last couple
>> > of years, then I don't think we need to urgently f
2011/12/31 Andras Timar
> 2011/12/31 Andras Timar :
> >
> > As for the Insert Rows/Columns modal dialog, it was a good catch that
> > needs to be fixed. But if it have been good enough for the last couple
> > of years, then I don't think we need to urgently fix it in 3.5 and
> > break the string
Dňa 31.12.2011 13:56, Andras Timar wrote / napísal(a):
> 2011/12/31 Martin Srebotnjak :
>> I guess the conservatism of OOo team when designing UI with those UI spec
>> documents was a good thing and this should be in a way incorporated in the
>> LO development process, even if with a lower adminis
Hi Mihkel,
2012/1/2 Mihkel Tõnnov :
> We have "Delete $1" and "Format $1" where $1 can be "Header" or
>> "Footer". Those are STR_HEADER and STR_FOOTER from
>> sw/source/ui/docvw/docvw.src and are not used anywhere else, so you
>> can translate them as you need to fit into the "Delete $1" context.
2011/12/31 Andras Timar
> 2011/12/31 Martin Srebotnjak :
> >
>
> So, Andras, will you take care of these two string-formations in the code
> > for 3.5, the one reported by Milos and the one by Mihkel? Or do we have
> to
> > adapt our translations according to "what the author of code wanted to
>
2011/12/31 Andras Timar :
>
> As for the Insert Rows/Columns modal dialog, it was a good catch that
> needs to be fixed. But if it have been good enough for the last couple
> of years, then I don't think we need to urgently fix it in 3.5 and
> break the string freeze. Let's fix it in master. What d
2011/12/31 Martin Srebotnjak :
>
> I guess the conservatism of OOo team when designing UI with those UI spec
> documents was a good thing and this should be in a way incorporated in the
> LO development process, even if with a lower administration impact on
> developers - but there should be some l
Quite. Even the little compounding we have leads to problems in highly
inflected languages. Yes/No is another of those, which is unfortunately
one that the OO team forgot, because a great many languages don't have a
single word for yes and no and rely on the repetition of the verb.
The only wa
Hi Donald et. al.,
2011/12/29 Donald Rogers
>
> On the other hand, is this a mechanism for developers to save us lots of
> work, retranslating the same strings over and over, e.g. OK, Cancel?
>
this is not a proper reason to compound strings this way. There are tons of
Cancels and OKs in the st
On 29/12/2011, at 2:52 PM, Mihkel Tõnnov wrote:
> Hi Milos, Martin, *,
>
> 2011/12/29 Martin Srebotnjak :
>>
>> 2011/12/28 Martin Srebotnjak
>>>
>>> 2011/12/28 Milos Sramek
>>>
Hi,
I have in the new Header/Footer feature of 3.5 for the first time
noticed compound string
Hi Milos, Martin, *,
2011/12/29 Martin Srebotnjak :
>
> 2011/12/28 Martin Srebotnjak
>>
>> 2011/12/28 Milos Sramek
>>
>>> Hi,
>>>
>>> I have in the new Header/Footer feature of 3.5 for the first time
>>> noticed compound strings consisting of two separately translated
>>> strings. For example, "
OMG, now I saw it, this is horrible - each context menu command must be a
separate string, you cannot format context menu commands in the same manner
for 100+ languages!
Thanks, Milos, for noticing this.
Lp, m.
2011/12/28 Martin Srebotnjak
> Hi, I haven't noticed that, this should be marked, ex
Hi, I haven't noticed that, this should be marked, explained in notes, if
sdf had those...
Will check, but why is this not a single string?
Does that mean that also "Format Footer" is formed from two strings?
This is unacceptable and anglo-saxon-centric, really does not work well for
other language
Hi,
I have in the new Header/Footer feature of 3.5 for the first time
noticed compound strings consisting of two separately translated
strings. For example, "Format Header" is composed of strings Format
(KeyId _XDs) and Header (b4n3).
Slovak (and other languages) have cases - the Header word must
14 matches
Mail list logo
