Re: Patch to reduce the number of messages to translate

By replacing type names we are creating a potential confusion.
A translator who is not familiar with the code may translate
type names like "long" or "integer".

I am for leaving the strings as they are. Translators are
copy+paste then edit the messages anyways.

Best regards,
Nicolai


On Tue, 21 Dec 2004 14:47:41 +0100, Xavier Poinsard <xpoinsard@free.fr> wrote:
> Here is the modified patch with hopefully no adjective problems.
>
> The changes are now the following :
>
> - "Conversion of box failed: {0}." => "Conversion to type {1} failed: {0}."
>   with box,circle,line,lseg,point
>
> - "The JVM claims not to support the ASCII encoding." => "The JVM claims
> not to support the {0} encoding."
>   with ASCII,UTF-8
>
> - "Bad byte: {0}" => "Bad value for type {1}: {0}"
>   with byte,short,int,long,BigDecimal,float,double,date
>
> - "Cannot cast an instance of {0} to Types.BIT" => "Cannot cast an
> instance of {0} to type {1}"
>   with Types.BIT,Types.OTHER
>
> Peter Eisentraut wrote:
> > You could rephrase the messages like this:
> >
> >     invalid input value for type "{0}": {1}
> >
> > Then there should be no problem.
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>
>
>