You are viewing a plain text version of this content. The canonical link for it is here.
Posted to l10n@openoffice.apache.org by kj...@kemedhaug.net on 2013/10/03 14:52:03 UTC

Is text segment lost?

Is there something missing from the English text?

-----------------
File: dbaccess/source/ui/querydesign.po
Locations: query.src#STR_ERROR_PARSING_STATEMENT.string.text

$object$ is based on an SQL command which could not be parsed.(except  
"SQL command", which doesn't make sense here) will be inserted.
-----------------
  It seems to me like it is missing something in the middle, between  
the period and the opening parenthesis.

I envision a variable/placeholder, perhaps for some component of  
$object$ which has been parsed successfully. Also, the quoted "SQL  
command" looks a little out of place.

Even if it is correct as it is, I find myself unable to translate the  
string without knowing the context.

Sincerely
Kjell


---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Is text segment lost?

Posted by Josef Latt <Jo...@gmx.net>.

Am 04.10.2013 21:57, schrieb Andrea Pescetti:

> But indeed this is a matter of taste. For example, I didn't like the
> "More..." appearing in the status bar menu for language selection (it
> was translated as "Extra..." in Italian). In Italian, we translated it
> as if it was "More languages". This has advantages (clearer for users)
> and drawbacks (not a 1:1 translation, with all possible consequences,
> especially if that string is reused out of context). In this case, the
> right solution is probably to ask that the English string is improved, see
> https://issues.apache.org/ooo/show_bug.cgi?id=123425

IMHO "More languages" isn't the right wording as the dialog which pops
up clicking on "More..." is named "Zeichen" in German UI. May be
"Character" in English UI.
This dialog has least to do with languages.

Therefore I would let as it is.

Regards

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Is text segment lost?

Posted by Andrea Pescetti <pe...@apache.org>.
Josef Latt wrote:
>>> I remember fixing it in only one English string. If you find more, please
>>> provide their IDs here.
> https://translate.apache.org/de/aoo40/translate.html#unit=12743681

This is another occurrence indeed. But both were fixed at the time:

http://svn.apache.org/viewvc/openoffice/trunk/main/dbaccess/source/ui/querydesign/query.src?r1=1505405&r2=1505404&pathrev=1505405

In the 4.0.x strings, the ones currently being used on Pootle, the fix 
is not visible; the fix is in the 4.1.x strings.

> [Jan] And btw I prefer to have a translation that match
> the en-US version, instead of a translation that match a potential future
> version (who knows if it will be changed again).

Here the reason is that this is a clear error. We are translating what 
was meant to be there. If the string changes again, probably it will be 
flagged for review in Pootle anyway.

But indeed this is a matter of taste. For example, I didn't like the 
"More..." appearing in the status bar menu for language selection (it 
was translated as "Extra..." in Italian). In Italian, we translated it 
as if it was "More languages". This has advantages (clearer for users) 
and drawbacks (not a 1:1 translation, with all possible consequences, 
especially if that string is reused out of context). In this case, the 
right solution is probably to ask that the English string is improved, see
https://issues.apache.org/ooo/show_bug.cgi?id=123425

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Is text segment lost?

Posted by Josef Latt <Jo...@gmx.net>.

Am 03.10.2013 21:39, schrieb janI:

>> I remember fixing it in only one English string. If you find more, please
>> provide their IDs here.

https://translate.apache.org/de/aoo40/translate.html#unit=12743681

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Is text segment lost?

Posted by janI <ja...@apache.org>.
On 3 October 2013 21:30, Andrea Pescetti <pe...@apache.org> wrote:

> kjell wrote:
>
>> Yes, if only the first clause should be there, it makes better sense.
>> The "surplus" should be removed from the English too, then, right?
>>
>
> It is already, but for version 4.1.x. You are currently translating
> version 4.0.x since it is the latest stable one.
>
> In general, remember that you can often find solutions in the mailing list
> archives: http://openoffice.apache.org/**mailing-lists.html#**
> localization-mailing-list-**public<http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public>
>
> For example, if you search "$object$" in http://markmail.org/search/+**
> list:org.apache.incubator.ooo-**l10n<http://markmail.org/search/+list:org.apache.incubator.ooo-l10n>you will find the other discussions about this problem.
>
>  I see the same incomplete clause is also added in a few other places,
>> probably
>> an accidental paste. I will remove it where it doesn't make sense.
>>
>
> I remember fixing it in only one English string. If you find more, please
> provide their IDs here.
>
>  Also, I use several other support languages (Swedish, German and
>> Danish), and all of them have the unwanted content translated verbatim.
>> Not sure whether I have access to those areas, but I will have a look,
>> given time...
>>
>
> Strange that they have the wrong content, this has been discussed at
> length here. Anyway, you can currently edit other languages too, even
> though this is set to change in future (we will enable translators for
> specific languages).
>

not strange, just a timing issue, the danish string was translated before
the discussion broke out. And btw I prefer to have a translation that match
the en-US version, instead of a translation that match a potential future
version (who knows if it will be changed again).

rgds
jan I.


>
> Regards,
>   Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.**apache.org<l1...@openoffice.apache.org>
> For additional commands, e-mail: l10n-help@openoffice.apache.**org<l1...@openoffice.apache.org>
>
>

Re: Is text segment lost?

Posted by Andrea Pescetti <pe...@apache.org>.
kjell wrote:
> Yes, if only the first clause should be there, it makes better sense.
> The "surplus" should be removed from the English too, then, right?

It is already, but for version 4.1.x. You are currently translating 
version 4.0.x since it is the latest stable one.

In general, remember that you can often find solutions in the mailing 
list archives: 
http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public

For example, if you search "$object$" in 
http://markmail.org/search/+list:org.apache.incubator.ooo-l10n you will 
find the other discussions about this problem.

> I see the same incomplete clause is also added in a few other places, probably
> an accidental paste. I will remove it where it doesn't make sense.

I remember fixing it in only one English string. If you find more, 
please provide their IDs here.

> Also, I use several other support languages (Swedish, German and
> Danish), and all of them have the unwanted content translated verbatim.
> Not sure whether I have access to those areas, but I will have a look,
> given time...

Strange that they have the wrong content, this has been discussed at 
length here. Anyway, you can currently edit other languages too, even 
though this is set to change in future (we will enable translators for 
specific languages).

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Is text segment lost?

Posted by kj...@kemedhaug.net.
Siterer Dick Groskamp <th...@quicknet.nl>:

> Op 3-10-2013 14:52, kjell@kemedhaug.net schreef:
>> Is there something missing from the English text?
>>
>> -----------------
>> File: dbaccess/source/ui/querydesign.po
>> Locations: query.src#STR_ERROR_PARSING_STATEMENT.string.text
>>
>> $object$ is based on an SQL command which could not be  
>> parsed.(except "SQL command", which doesn't make sense here) will  
>> be inserted.
>> -----------------
>> It seems to me like it is missing something in the middle, between  
>> the period and the opening parenthesis.
>>
>> I envision a variable/placeholder, perhaps for some component of  
>> $object$ which has been parsed successfully. Also, the quoted "SQL  
>> command" looks a little out of place.
>>
>> Even if it is correct as it is, I find myself unable to translate  
>> the string without knowing the context.
>>
>> Sincerely
>> Kjell
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: l10n-help@openoffice.apache.org
>>
>>
>>
> No, nothing missing.
> You should ignore/delete everything after the period.
>
> The part between parenthesis should be removed
>
> And yes, $object$ is indeed a placeholder that couldn't be parsed.
>
> Leave "$object$" as it is
> and translate "is based on an SQL command which could not be parsed."
>
> That should be all, leave everything else out.
>
> String refers to a command what was written in SQL but that could  
> not be ran (parsed).
> Maybe because of a wrong word or operator in the SQL command
>
> Hope it is claerer so
>
> -- 
> DiGro

Yes, if only the first clause should be there, it makes better sense.  
The "surplus" should be removed from the English too, then, right? I  
see the same incomplete clause is also added in a few other places,  
probably an accidental paste. I will remove it where it doesn't make  
sense.

Also, I use several other support languages (Swedish, German and  
Danish), and all of them have the unwanted content translated  
verbatim. Not sure whether I have access to those areas, but I will  
have a look, given time...

Thanks!


---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Is text segment lost?

Posted by Dick Groskamp <th...@quicknet.nl>.
Op 3-10-2013 14:52, kjell@kemedhaug.net schreef:
> Is there something missing from the English text?
>
> -----------------
> File: dbaccess/source/ui/querydesign.po
> Locations: query.src#STR_ERROR_PARSING_STATEMENT.string.text
>
> $object$ is based on an SQL command which could not be parsed.(except 
> "SQL command", which doesn't make sense here) will be inserted.
> -----------------
>  It seems to me like it is missing something in the middle, between 
> the period and the opening parenthesis.
>
> I envision a variable/placeholder, perhaps for some component of 
> $object$ which has been parsed successfully. Also, the quoted "SQL 
> command" looks a little out of place.
>
> Even if it is correct as it is, I find myself unable to translate the 
> string without knowing the context.
>
> Sincerely
> Kjell
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: l10n-help@openoffice.apache.org
>
>
>
No, nothing missing.
You should ignore/delete everything after the period.

The part between parenthesis should be removed

And yes, $object$ is indeed a placeholder that couldn't be parsed.

Leave "$object$" as it is
and translate "is based on an SQL command which could not be parsed."

That should be all, leave everything else out.

String refers to a command what was written in SQL but that could not be 
ran (parsed).
Maybe because of a wrong word or operator in the SQL command

Hope it is claerer so

-- 
DiGro
___________________________
Apache OpenOffice 4.0.0 (Dutch) and scanned with Ziggo extended security (F-Secure)


---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org