[Scilab-loc] Question to our localization specialist

[Ihor Rokach]

I think that in general such mistakes are unavoidable. The problem is we
(translators) sometimes have no chance to check even the basic features of a
new Scilab release in advance (there is no such things as release candidate
in this project). Scilab 5.3.2 was released without external testing, so the
result is as it is.

Additionally, in Scilab project there are no "service packs" or patches, to
fix the simplest bugs of the current stable release. 

These two tools can be used for fixing all types of bugs in Scilab, not only
those connected with localization.

With best wishes,
==
I.Rokach 

> -----Original Message-----
> From: Sylvestre Ledru [mailto:sylvestre.ledru at scilab.org]
> Sent: Thursday, May 19, 2011 10:48 AM
> To: localization at lists.scilab.org
> Subject: [Scilab-loc] Question to our localization specialist
> 
> Hello guys,
> 
> Since some of you are localization specialist, I would like to have some
> advices.
> 
> In the latest release of Scilab, a critical issue in the Polish and
> Japanese localizations has been found. This causes a bad exception and
> Scinotes to be unusable:
> http://bugzilla.scilab.org/show_bug.cgi?id=9475
> 
> I was wondering if you know any tool which might check the quality of
> the translation regarding the programming language.
> 
> For example, in Scilab, I will write:
> myString = "I don''t known"
> 
> Some translators are not very familiar with specificities of languages.
> They might think the double quote might just be a typo and remove it
> from the translated string.
> This is bad since it breaks the execution since the string is badly
> formatted.
> 
> Do you know a tool which might here ? (it is hard for us to test Scilab
> in all the languages).
> 
> Thanks,
> Sylvestre