greenwood
Posts: 2
|
| Posted: 03/08/2007, 10:09 AM |
|
Not sure if it's because I'm using the eval version at the moment, anyway while checking if CCS is suitable for my next project I came across a couple of annoying aspects using internationalisation (this is using English and Spanish dynamically).
So for the workarounds:
1) Mixed English and Spanish language appearing on Record forms.
For some weird reason English would appear in css_RecordFormPrefix and Spanish in the suffix. Placing a space in the Spainsh css_RecordFormPrefix removed the English from this form. Not sure if it is a bug or forced some code somewhere to be recompiled.
2) Capitilised words not being translated.
I have employee and Employee that need to be translated. employee translates fine yet Employee does not. As I can not add Employee using the resource editor, it twitters on about duplicate entries, editing en.txt and es.txt (while the project is closed) and adding the entries by hand fixes this problem. It generates a warning when publishing about duplicate entries but at least both now get translated. A side note is that only one of the entries will show up in the resource editor.
|
 |
 |
wkempees
|
| Posted: 03/08/2007, 11:44 AM |
|
Greenwood,
If you are sure you found bug, please report to support.
But:
> Not sure if it's because I'm using the eval version at the moment, anyway
> while
> checking if CCS is suitable for my next project I came across a couple of
> annoying aspects using internationalisation (this is using English and
> Spanish
> dynamically).
There should be no different behaviour on Internationalization between trial
and full version, afaik.
>
> So for the workarounds:
>
> 1) Mixed English and Spanish language appearing on Record forms.
>
> For some weird reason English would appear in css_RecordFormPrefix and
> Spanish
> in the suffix. Placing a space in the Spainsh css_RecordFormPrefix removed
> the
> English from this form. Not sure if it is a bug or forced some code
> somewhere
> to be recompiled.
At first sight this looks like normal behaviour.
at first your Prefix did not contain a translation, so the default language
will be used.
This gives you the opportunity to add a language, do some translating, next
go through your
application and see the translations you have skipped or not done yet.
Also it does provide a good application, one without HOLES.
As you stated you placed a space in the spanish Prefix, in fact translating
it, and that solved the problem.
A space in the English version would have had the same effect btw.
>
> 2) Capitilised words not being translated.
>
> I have employee and Employee that need to be translated. employee
> translates
> fine yet Employee does not. As I can not add Employee using the resource
> editor, it twitters on about duplicate entries, editing en.txt and es.txt
> (while the project is closed) and adding the entries by hand fixes this
> problem. It generates a warning when publishing about duplicate entries
> but at
> least both now get translated. A side note is that only one of the entries
> will
> show up in the resource editor.
Now this one I don't know, have not seen a similar problem at my end.
So maybe this would be a good onefor support!
Greetings Saludos
WalterWalter (translated nicely, lol)
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
wkempees
|
| Posted: 03/08/2007, 11:45 AM |
|
Oeps,
Just noted this is in Tips-and-Solutions.
Yours is a question, so wrong forum.
My answer is wrong too as dicussion should not take place here, Sorry.
Walter
"greenwood" <greenwood@forum.codecharge> schreef in bericht
news:2545f051649ebef@news.codecharge.com...
> Not sure if it's because I'm using the eval version at the moment, anyway
> while
> checking if CCS is suitable for my next project I came across a couple of
> annoying aspects using internationalisation (this is using English and
> Spanish
> dynamically).
>
> So for the workarounds:
>
> 1) Mixed English and Spanish language appearing on Record forms.
>
> For some weird reason English would appear in css_RecordFormPrefix and
> Spanish
> in the suffix. Placing a space in the Spainsh css_RecordFormPrefix removed
> the
> English from this form. Not sure if it is a bug or forced some code
> somewhere
> to be recompiled.
>
> 2) Capitilised words not being translated.
>
> I have employee and Employee that need to be translated. employee
> translates
> fine yet Employee does not. As I can not add Employee using the resource
> editor, it twitters on about duplicate entries, editing en.txt and es.txt
> (while the project is closed) and adding the entries by hand fixes this
> problem. It generates a warning when publishing about duplicate entries
> but at
> least both now get translated. A side note is that only one of the entries
> will
> show up in the resource editor.
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
greenwood
Posts: 2
|
| Posted: 03/08/2007, 2:22 PM |
|
Quote wkempees:
At first sight this looks like normal behaviour.
at first your Prefix did not contain a translation, so the default language
will be used.
This gives you the opportunity to add a language, do some translating, next
go through your
application and see the translations you have skipped or not done yet.
Also it does provide a good application, one without HOLES.
As you stated you placed a space in the spanish Prefix, in fact translating
it, and that solved the problem.
A space in the English version would have had the same effect btw.
The problem came about as the English resource has a prefix and the Spanish one has a suffix, with the locale set to English only the prefix appears as is expected. When the locale is set to Spanish, you get the English prefix and the Spanish suffix, if it is normal behaviour then it should be documented that a space is needed to be placed in the blank ebtries to supress that word. I guess falling back to the default language when no entry is set is probably the best way for the application to respond.
I'm sure this will be moved if it's in the wrong place :)
and support case submitted
|
|
|
|
|
