Am 12/22/2012 07:41 PM, schrieb janI:
I have nothing a little extra work, if I other for much more work...no
problem.
I tested your idea, and it works with one big exception:
<xxx>
some of the<xx> are used for control commands:
<bold> ...<variable id=jan1>
and I do not think it is a good idea to change that.
But until now, I have only found 2 places where<> is used and should be
translated
cmd -p<filename>
and those could be easily changed
Can I find these 2 examples in the patch in the respective BZ issue that
you've opened? Just to see the variables in their context.
or do you see it differently ?
I've no clue about the code itself. However, when it's just about these
2 exceptions for the <xxx> variable syntax that should be translated,
then maybe it's OK to change the style to a different syntax - just to
go around the problem.
Then everything in <xxx> and with the postfix "-nt" must not be translated.
My 2 ct.
Marcus
On 22 December 2012 12:38, Marcus (OOo)<marcus.m...@wtnet.de> wrote:
Am 12/22/2012 12:35 PM, schrieb janI:
I like you idea !!! much easier to handle, the implementation might be a
little more complicated, because I have to poke around in the code to see
where the variables are used.
Yes, the initial work is maybe a bit more than wanted. However, the
communication with our l10n people what to translate and what not could
become really easy.
thanks for the idea.
:-)
Marcus
On 22 December 2012 12:31, Marcus (OOo)<marcus.m...@wtnet.de> wrote:
Am 12/21/2012 11:00 PM, schrieb janI:
For general information, I have added a new bug 121536, regarding
problems
with translations.
The content of the msg text in the source code is non translatable due
to
ambiguity.
[xxx] means normally a variable will be inserted here
example: "[Time]" may NOT be translated but "[l]" (for load) should be
translated.
<xxx> means normally XML and should not be translated:
example: "<variable id="jan">hello</variable>" may NOT be translated but
"-p<file>" should be translated.
$xxx means normally a variable will be inserted here
example: "$id" may NOT be translated but "$100" dollar should be
translated.
Now try to explain that to our translators, it is easier to change the
source texts !
If nobody objects I will solve this bug, alongside with the oracle
changes.
What about to write these special variables with "nt" as postfix. Adding
this to the variable name inicates that no translation is wanted or must
not happen at all.
To stick with your example from above it would look like this:
[xxx] translation wanted
[xxx-nt] no translation wanted
<xxx> translation wanted
<xxx-nt> no translation wanted
$xxx translation wanted
$xxx-nt translation wanted
Maybe a possible way around the problem?
