Hi Bob,
I thought again about this translation business. What is the current status
?
If I understood correctly :
- There's 1 text having a [...] that should be kept in the displayed text
("bad [R, G, B] color")
- 1 or 2 texts having a [...] that should be removed in the displayed
text
- The code removes [...] in the displayed text when it is at the
beginning or the end of the text
I would suggest an other approach :
- Using [[...]] instead of [[...]] for text that should be removed in the
displayed text. This is really unlikely that we would need a text with that
construction.
- Replacing the 1 or 2 texts having a [...] that should be removed by the
[[...]] construction
- The translated text can keep the [[...]] part or remove it
- Modifying the code for removing [[...]] in the displayed text wherever
it is
For making current English texts more explicit, I suggest the following
approach :
- Tell me which English texts need to be modified and by what they should
be replaced
- I will change the Java code and the existing .po files so that we can
keep the existing translations (it should be a simple matter of
finding/replacing text in all the .po files)
- Launchpad will update itself automatically when I commit the Java files
and the .po
What do you think ?
Nico
On Tue, Oct 4, 2011 at 2:18 PM, Robert Hanson <[email protected]> wrote:
> I've at least put in the [....] business (starting or end of line) for Jmol
> 12.3.1. I saw there was one already in there anyway.
>
>
> 2011/10/4 Angel Herráez <[email protected]>
>
>> In my opinion, being able to make distinctions between phrases that
>> translate different. There are a few other instances that I would
>> like to improve in the future (like no, none, ...)
>>
>> It is of course clear that we need a mechanism that does not break
>> existing translation and requires the least of custom per-case
>> editing (which is what we suffer now)
>>
>> We can discuss choices without a hurry, for 12.3
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1
>> _______________________________________________
>> Jmol-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jmol-developers
>>
>
>
>
> --
> Robert M. Hanson
> Professor of Chemistry
> St. Olaf College
> 1520 St. Olaf Ave.
> Northfield, MN 55057
> http://www.stolaf.edu/people/hansonr
> phone: 507-786-3107
>
>
> If nature does not answer first what we want,
> it is better to take what answer we get.
>
> -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Jmol-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jmol-developers
>
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
