Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Libraries and TheIDE: i18n, Unicode and Internationalization » how to Internationalize my app?
Re: how to Internationalize my app? [message #3349 is a reply to message #3347] Sun, 21 May 2006 11:35 Go to previous messageGo to previous message
forlano is currently offline  forlano
Messages: 1215
Registered: March 2006
Location: Italy
Senior Contributor
luzr wrote on Sun, 21 May 2006 10:00

forlano wrote on Sun, 21 May 2006 03:13


#define TFILE <CtrlLib/CtrlLib.t>
#include <Core/t.h>
[/code]



Sorry for confusing you, TFILE here is just an example (copied straight from CtrlLib package), it should point to your .t (inside your package).

Mirek


OK, now it works Smile , but there is still a new problem that I didn't expect. The following translation works:
T_("{{1@5 [@9= This is the]::@2 [A5@0 Ultimate`+`+ Hello world sample}}")
itIT("{{1@5 [@9= Questa e' l'esempio]::@2 [A5@0 di Ultimate`+`+ Hello world}}")

But I've used a workround to let it to work. In fact instead of "e'" I should use "è" ('e' with accent all in one character). But this produces the following message:
"ERROR: invalid UTF-8 sequence..."
Is this normal?

In order to change all the interface message at the start of the application I guess I need to save the selected language change in a configuration file.

Last consideration. In this way the message.t file is compiled and the user has not the possibility to change the translation if it has not the source code of the application. I wonder if in U++ there is a smart way to distribute the application with some message file that the user can modify as it likes. For example he can fill all the ruRU translation without to bother me asking a new compilation. This file should be loaded by the application when it starts. I've done it for my old app, but with t_(...) his manteinance should be greatly simplified.

Luigi
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Non-english symbols unreadable [solved w/ SetDefaultCharset]
Next Topic: Spacing problems with FileSel...
Goto Forum:
  


Current Time: Wed Aug 27 01:04:26 CEST 2025

Total time taken to generate the page: 0.09758 seconds