Hi :)
My last "hare-brained" idea was blatantly flawed. Thanks to Yury (i think)
and someone else for shooting it down quickly before it went anywhere! :)
Sorry about that!
It sounds like there is scope for a lot of automation. There might already
be ways of doing it.
1. Can fuzzy strings be a
Done.
But some dev should push it into the 4.4 brach. I can't.
regards
Olivier
On 14/12/2014 09:55, Jean-Baptiste Faure wrote:
> Hi Olivier,
>
> Thank you very much. :-)
>
> Best regards.
> JBF
>
> Le 14/12/2014 12:53, Olivier Hallot a écrit :
>> Hi Jean Baptiste,
>>
>> I wrote that. I can f
hi,
2014.12.14 13:48, Olivier Hallot wrote:
> On 14/12/2014 06:59, Rimas Kudelis wrote:
>> It should be. You can look at it the other way around: anything that
>> gets in the source should consistently be en_US, not just
>> whatever_lingo_the_developer_had_in_mind.
>>
>> Rimas
> You're right and t
Hi Olivier,
Thank you very much. :-)
Best regards.
JBF
Le 14/12/2014 12:53, Olivier Hallot a écrit :
> Hi Jean Baptiste,
>
> I wrote that. I can fix it. ERF and ERF.PRECISE are the same function
> with different names, introduced to comply with MS.
>
> Regards,
> Olivier
>
> On 14/12/2014 09:
Hi Jean Baptiste,
I wrote that. I can fix it. ERF and ERF.PRECISE are the same function
with different names, introduced to comply with MS.
Regards,
Olivier
On 14/12/2014 09:15, Jean-Baptiste Faure wrote:
> Hi,
>
> Do you agree that there is an error in the help for ERF.PRECISE function ?
>
>
Hi
On 14/12/2014 06:59, Rimas Kudelis wrote:
> It should be. You can look at it the other way around: anything that
> gets in the source should consistently be en_US, not just
> whatever_lingo_the_developer_had_in_mind.
>
> Rimas
You're right and that is the way it has to be.
We face the issue
Hi,
Do you agree that there is an error in the help for ERF.PRECISE function ?
In scalc/01.po arround line 38160
#. X74ZA
#: 04060115.xhp
msgctxt ""
"04060115.xhp\n"
"par_id2963824\n"
"138\n"
"help.text"
msgid "ERF(LowerLimit; UpperLimit)"
should be
...
msgid "ERF.PRECISE(LowerLimit; UpperLimit)
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 o
Khaled,
Well, then your locale is lucky to have you and/or your team. Probably a
language with several million speakers. Lucky you. Unfortunately many
teams are tiny and rely on the same localizers who usually handle
multiple projects. And before you say grow your team, there's only so
much g
Khaled,
Sgrìobh Khaled Hosny na leanas 14/12/2014 aig 06:35:
but the way people is complaining about them is what I'm worried about
as it shows that some localiser seem to have total disregard to things
that are intrinsic to the quality of any textual material, let alone
localisation.
I resen
On Dec 14, 2014 8:41 AM, "Yury Tarasievich"
wrote:
>
> 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 localis
On 12/14/2014 11:59 AM, Rimas Kudelis wrote:
2014.12.14 02:43, jonathon wrote:
...
The more fundamental error is assuming that what is in source is
consistently en_US, or any other en_* variant.
It should be. You can look at it the other way around: anything that
gets in the source should con
Hi,
2014.12.14 02:43, jonathon wrote:
> On 13/12/14 21:45, Khaled Hosny wrote:
>
>>> Changes made in one dialect of one language should neither affect, nor
>>> effect changes in other dialects of the same language, much less other
>>> languages.
>> Huh? English (US) is the “source” language,
> Tr
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
Hi Yury, all
Le 14/12/2014 07:41, Yury Tarasievich a écrit :
> 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 lo
On 14/12/14 06:35, Khaled Hosny wrote:
> total disregard to things that are intrinsic to the quality of any textual
> material, let alone localisation.
Look at it this way.
There are 10,000 strings to translate.
At current rates, a professional translator will charge between
US$20,000 and US$2
16 matches
Mail list logo
