[etoys-dev] Re: Need for translation in DrGeo
korakurider at gmail.com
Sat May 15 18:17:50 EDT 2010
I changed the subject to get appropriate folks take look at the problem..
On Sun, May 16, 2010 at 2:57 AM, Hilaire Fernandes
<hilaire.fernandes at edu.ge.ch> wrote:
> I am afraid localization of tiles does not work.
> I can not get it translated in the viewer.
> I did have extracted the string in DrGeoII.pot
> I did merge the DrGeoOO.pot with the fr.po
> I translated and compiled the fr.po to DrGeoII.;o
> I installed this DrGeoII.mo in the french locale for Etoys
> In Etoys, all DrGeo messages are translated but the tiles in the viewer.
> What did I miss?
This is known problem of current implementation. Translation stuff is
assuming all of tile strings belong to default domain. And in which
POT do you see your tile string?
(I imagine etoys.pot) Sorry for not mentioning this when I answered
about marking strings...
To resolve the problem, case(2) in
needs to be addressed.
We really need to try hard to resolve this if we go with package based
splitting of translation...
> Korakurider a écrit :
>> Hi Hilaire
>> On Sat, May 15, 2010 at 1:26 AM, Hilaire Fernandes
>> <hilaire.fernandes at edu.ge.ch> wrote:
>>> Btw, what is the proper way to mark tiles for translation in code like
>>> ^ # (drgeo (
>>> (slot curveAbscissa 'The abscissa of this point on the curve' Number
>>> readWrite Player getCurveAbscissa Player setCurveAbscissa:)
>>> (slot Xw 'The x coordinate in the DrGeoII world coordinate system' Number
>>> readWrite Player getWorldX Player setWorldX:)
>>> (slot Yw 'The y coordinate in the DrGeoII world coordinate system' Number
>>> readWrite Player getWorldY Player setWorldY:)
>> You don't need to mark them.
>> GetTextExporter2 extracts automatically strings from method with name
>> starting from addtionsToViewerCategory. Review
>> Please let us know if you see missing strings in extracted POT.
>>> etoys-dev mailing list
>>> etoys-dev at squeakland.org
More information about the etoys-dev