[Gambas-devel] Translating missing

[Ron Onstenk]

On Wednesday 10 November 2004 21:29, Laurent Carlier wrote:
| Le Mardi 9 Novembre 2004 20:31, Ron Onstenk a écrit :
| > On Tuesday 09 November 2004 13:44, Laurent Carlier wrote:
| > > Le Mardi 9 Novembre 2004 12:46, Benoit Minisini a écrit :
| > > > > And should there not be a list with those Error.Text to translate ?
| > > >
| > > > Yes. Later :-)
| > >
| > > Does it shall be a good way to add constants for error beside translating
| > > them as it will be easy to manage errors like in glibc
| > >
| > > eg : Constant Error.NotObject for a "Not an Object" error will be print
| > > as "N'est pas un objet" in french
| >
| > I belive it ie already there as Error.Code ??
| >
| 
| Sure, Error.Code exist. But can you say me what is the meaning of the value of 
| 10 as example ? 
| 
| Perhaps it can be guess with Error.Text but how to do when it will be 
| translated ?
| 

I have some back talk with one from the KDE translate team.
He says the policy is not to find for everey word an translation 
in the develop environment.
I agree to that, because if something is unclear you need to lookup
on the net and then you must search for the English word(s) and not the
local language for help.

The Error messages are at primary level for the developer and if they
occur it is by an unfore seen event by the developer.
For looking up on the net, you understand English is the best, however 
a good explanation in the the local language can be more helpfull, I
agree to that. I miss the explanation sometimes also, not what but why.

For your example question 'What is Error.code 10' you can look in gberrors.c
in the source tree. Not a very convince way but for a developer usable.
May be a hint to place a lookup table in the 'Help' with it.

For the end user the developer should make his own error trapping and present
the message in the local language in case a mistake has done by the user.
This will make the applications more complex for transfer to other users on the world.

Personal I believe the IDE or UI should be translated at a very minimum, 
the action words can but not the terms like 'file' or say the objects 
on which the action is done. i.e. 'Save file' to 'Opslaan file'

Maybe a 'Error.class' in the project with code to local language text AND 
a explanation is a better way.
This can be made as separate project and included with 'USE' in gambas for
the project.

| My suggestion is with constants like the color class in qt component 
| (color.black ... p.e.).
| 
| Regards,
| 

I believe here it can't be translated. Simple because the words are the
symbols (like icons) for the value. Black means the numeric value of 1.
How if the code is made by English people with 'Black' and are
used by Dutch, where 'Black' is 'Zwart' ? As example:

  IF textbox.foreground = color.black THEN  'will be translated in Dutch
  IF textbox.foreground = color.zwart THEN  'or translated to much as
  ALS tekstdoos.voorgrond = kleur.zwart DAN

It is not impossible to do but if people cut and past in a e-mail it make 
no sense anymore :)
Here it make for me more sense and proves not to translate every thing,
but use a more common language as English as it is now.

I'm not happy with all the translating I have done till now,
I believe I did from developer view to much after all.
But my first intention was to get as much as possible the nl.po
file updated to the situation Gambas is now.

The correct was second to it and maybe I undo some translating the next
versions for some terms. 
The word 'package' is translated but I'm very unhappy with it.

After being busy with the translating to Dutch I can say it is
more complex and less easy as I already was afraid it should be.

Ron