Re: 0.90 RC2 Installation Problem: Fewer translated items than expected.

[Cyrille Chepelov <cyrille chepelov org>]

Le Sun, May 26, 2002, à 11:43:45PM -0300, Dolores Alia de Saravia a écrit:

> Inrefaz de Usuario, 
> Diagram Defaults,
> Ver opciones por Defecto,
> Linea de cuadricula,
> Diagram Tree  

Please verify there are no *fuzzy* translations in es.po, and no
untranslated strings. I see (downstairs) there are some problems, indeed.

 
> (I have just paid attention to the following: during make I get many 
> warnings; 
> 
>  and one error:
> 
> diaconv.c: In function `main':
> diaconv.c:125: warning: passing arg 3 of `poptGetContext' from 
> incompatible pointer type
> Traceback (most recent call last):
>   File "./checktrans.py", line 24, in ?
>     from xml.sax import saxexts
> ImportError: No module named xml.sax

this means you don't have a complete Python system installed. You lack
python-xml. This is not critical to building dia, only
core-translation-report.
  
> but I can execute run_dia.sh.... 
> ) 
> 
> Any way, I attach a file mentioning some very few errors in es.po,  and
> proposing some translations. 

Please forward this to the Spanish language team.


> #. choose default font name for your locale. see also font_data structure 
> #. in lib/font.c. 
> #: objects/FS/function.c:417 objects/SADT/annotation.c:357 
> #: objects/UML/actor.c:332 objects/UML/classicon.c:415 
> #:objects/UML/component.c:348 objects/UML/message.c:369 
> #: objects/UML/node.c:328 objects/UML/object.c:447 objects/UML/state.c:340 
> #: objects/UML/usecase.c:387 objects/chronogram/chronoline.c:611 
> #: objects/chronogram/chronoref.c:434 
> #, fuzzy 
> msgid "Helvetica" 
> msgstr "Helv?tica" 

STOP !!!

Unless the default Postscript name for the Spanish equivalent of the
Helvetica font is called Helvetica with a diacritic, translate it as
Helvetica (exactly as in English). Same happen with Courier. This is a major
pitfall of dia 0.90 for translators.

Akira: I told you there would be problems. I'm almost sure I avoided them in
fr.po, but I bet you we'll have printing problems which will be traceable to
this. We'll need a better way, in a relatively short time frame !

(what about defining some "font equivalent" tables, with for instance (using
Python dictionary syntax and imaginary font names and character range
constants :

 {
   'Helvetica': {        
	range(JAPAN_U_FIRST, JAPAN_U_LAST): "GothicBBB-Medium",
 	range(RUSSIA_U_FIRST, RUSSIA_U_LAST): "Helveticasky",
	range(EGYPT_U_FIRST,EGYPT_U_LAST): "Ramseselvetica",
	range(SYMBOL_U_FIRST,SYMBOL_U_LAST): "Symbol"
	}
   'Courier': {
	# etc.
	}
  }

This could be either compiled in, or in a text file, but the key point is:
this should be out of the translators way. Translators are doing an
outstanding job at translating, but outside translating I'm too afraid
they'll mess up the software.)



> ( o dejarlo sin traducir....; En es.po est? traducido por flotar vertical, 
>   lo cual sin duda es error
> 
> #: app/diagram_tree_menu.c:45
> #, fuzzy
> msgid "/_Sort objects"
> msgstr "_Ordenar objetos"
>   
>   (est? traducido "Objetos de diagrama de flujo", lo cual no es correcto; pero
>    no s? si hay que subrayar una s!!!)


You need to have the slash at the beginning of the translated string. This
fully explains why some menu entries appear in English in addition to
Spanish.

	-- Cyrille

> (Aunque nac? en Madrid, hace muchos a?os que vivo en Argentina)
> 
>  En Argentina usamos bastante la expresi?n   "valores  por defecto..." o
> "par?metros por defecto...". En ese sentido y para acortar los t?tulos, en
> lugar de las traducciones "explicadas completas", por ejemplo:

I don't totally understand; though if necessary, it is possible to have a
partial es_AR.po file where dialects diverge enough.

	-- Cyrille


-- 
Grumpf.