Re: [Web-erp-developers] Translation

[skaill <sk...@ro...>]

I would agree.  It is a fairly simple conversion and would introduxe an
error as opposed to screwing up the logic.  We are only putting in . and '
and _ ( ).  The only added concern is the possible booleans which will be
fine if everyone understands to translate them only when displayed.  The
booleans will be obvious because they will all have a 'Y' or 'N' hard coded
in an if statement.  That's what they're meant for.

If you see a 'Y' or 'N' then if you are not sure then DON'T change them.

Steve

----- Original Message ----- 
From: "Phil Daintree" <we...@pa...>
To: <web...@li...>
Sent: Friday, September 03, 2004 6:57 AM
Subject: Re: [Web-erp-developers] Translation


> This is quite a serious concern with this project. It would be most
> upsetting to introduce more problems than we resolve - I am very keen to
> keep the code stable. I am fairly confident (I think) that these changes
> will cause parsing errors if there is a mistake in the code ie missed
> out a . or closing ' or something so I am thinking that the page will be
> ok or it wont actually run. If it runs then there is a good chance that
> no logic errors will be introduced. The only area of concern is the use
> of submit buttons where I have tested for a returned value. In most
> cases these can be changed to isset.
>
> Phil
>
> On Thu, 2004-09-02 at 23:22, skaill wrote:
> > Sure, I think I can do those pages but I can only superficially test
them as
> > I'm honestly not that familiar with those areas and may not know if I've
> > introduced an error.  Unfortunately you may need to do some extended
testing
> > if you want to have good confidence in all the translation code changes.
> >
> > After we do each section we should get someone who is using webERP and
wants
> > translation to use it for a week or two to make sure there are no errors
> > with what we've done.  After that, proceed to the next set.
> >
> > The types of changes we are making theoretically should not get us into
much
> > trouble though.
> >
> > Although the value gets changed in the Submit (and other inputs) the
name
> > should remain the same to keep the code all in one language (English).
> >
> > One tricky circumstance is if 'Y' and 'N' have been used for boolean.
> > These values get stored as data.  The data cannot be translated from Y
or N
> > as stored or the logic test of if TestFlag == "Y" wouldn't work when you
> > changed languages.  It would work if you changed the right half but only
for
> > one language!  The best solution is to translate when displayed.
> >
> > It all has to do with display time as opposed to code logic.
> >
> > Steve
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers