Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
FoxyPreviewer 2.61
Message
From
28/07/2011 22:23:21
 
 
To
28/07/2011 16:08:27
General information
Forum:
Visual FoxPro
Category:
Third party products
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Miscellaneous
Thread ID:
01519458
Message ID:
01519534
Views:
48
Likes (1)
>>>>>Hi,
>>>>>
>>>>>when using FoxyPreviewer v2.61 and language Dutch I get instead of Kopie (copies) KopiÚ although the foxypreviewer_locs gives also Kopie for the translation of the cancopy field.
>>>>>Rebuilding of Foxypreviewer.app gave no result.
>>>>>How to solve this?
>>>>>
>>>>>Regards,
>>>>>
>>>>>Koen
>>>>
>>>>Is method SetLanguage calling _goHelper.GetLoc for every field on the form? The Copies field? I am using version 2.31, so i assume that 2.61 still uses _goHelper.
>>>
>>>Chris,
>>>Seriously, I would not know if method SetLanguage calling field cancopy correctly, I suppose so, otherwise where does he get the wording KopiÚ from? It seems to be a wrong conversion from Kopiën . (wrong conversion of ë into Ú) Once the word cancopy was (wrongly) translated into Kopiën and corrected on a later stage. I have a hinch this conversion was not effected.
>>>
>>>Dutch is not included in the testfiles, so I have to test with my own report / my own application. When I run the testfiles I can see that in other languages (e.g. German) the word 'cancopy' is correctly translated.
>>>
>>>Regards,
>>>Koen
>>
>>Hi Koen,
>>
>>I got the translation from Google, and replaced "KopiÚ" with "kopieën".
>>http://translate.google.com/#en|nl|copies
>>
>>Well, it was you who tranlated that file for me !!!
>>
>>Please get version 2.61a, that brings your "kopieën"
>>
>>Cheers
>
>
>Hi,
>
>Of course I knew that it was me who brought you firstly the wrong translation and I also remember to bring you the correction, that's why I was anxious to see how it came into effect. And of course it came!
>
>Very good my friend,
>
>thanx
>
>Koen
>
>P.S. May be some day you will tell me why it did not take effect in version 2.61?

ehehehehehe
Just because YOU made a typo mistake !!!
I just replaced the string :-)

That's all I did

Regards

Cesar
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform