Wt

Hey Dushan,

You should reference the resource bundle: const std::string PATH_TO_MESSAGES = "resources/text/strings" (i.e. without the xml)

The reason for this major gotcha (it has bitten me too a few times) is that it will append ".xml" or "_nl.xml" etc... depending on the locale.

Are you clocking the response time ? :-)

Regards,

koen

WHUUUSHHH!!

Look, up in the sky!

It's a plane !

It's a comet!

No , it's Koen writting responces in the Redmine! :D lol

Anyway , it seems you really know thing or two about this library , since the fix worked ,

Thank you :)

Do you think if it would be a good idea to put this into FAQ and/or documentation ?

Regs,

Dushan

Hi everybody,

I exactly have the same problem but just with Google Chrome. The same code works very well on Firefox but with chrome, every strings are unresolved and are displayed like key ...

Cheers,

Gaël

Probably a similar reason: a resource bundle that is not found. This should however not give different behaviour on Chrome vs Firefox.

Every string within a tr("key") should be found in a resource bundle, or it will be rendered as key. Did you restart your application from a different path? Did you run the two browsers simultaneously and observe this problem? Is the language setting of one browser different from the other?

BR,

Wim.

Thanks for your reply, Wim,

I resolved my problem ... it was in the language setting of my chrome browser... :/

EN in Chrome !

FR in Firefox !

Drrr!

Gaël

If one of your resource files doesn't have a language extension (mybundle.xml), it will be the default language bundle. If the key is not found in the language-specific resource file (mybundle_fr.xml), the default bundle will still be searched for that key.

Generally, it's not a bad idea to have a 'default' bundle that contains all your keys and translates them in some language.

Wim.

I have some problem.

Code:

class ServiceApp : public Wt::WApplication

{

public:

ServiceApp(const Wt::WEnvironment& env)

{

this->setLocale("");

this->messageResourceBundle().use(WApplication::appRoot() + "Service");

Wt::WText *name = new Wt::WText(root());

name->setText(Wt::WWidget::tr("test"));

}

}

String resources(D:\dev\wdi\Bin\Debug\Service\xml):

<?xml version="1.0" encoding="iso-8859-1" ?>

Test

I start the program like this:

service.exe ---http-address=0.0.0.0 ---http-port=8080 ---docroot=D:\dev\wdi\Bin\Debug

I get as a result of:

??test??

What am I doing wrong?

Thanks.

Sorry, path to xml is D:\dev\wdi\Bin\Debug\Service.xml

Hello Alexander,

The code looks fine.

There are two important paths in Wt that are different in an important way:

• docroot: points to the base directory of the files you want to serve through the built-in httpd. Every file in this directory or subdirectories thereof can be downloaded from your computer through HTTP when your application is running. You should set it to the directory that contains your css files, the resources directory, images, and other files that the browser needs access to while executing your application. In short, it is the directory that contains the files that the client can access.
• approot: this is a mechanism in Wt that allows you to specify where files that the application needs, but that are not intended to be served, reside. A translation bundle is indeed something that your application needs server-side, but a browser has no interest in downloading it. Other examples are database file locations, configuration files for your application, ... The use of approot is optional. Whenever you need to access a file on your local disk, we suggest that you write (wApp->appRoot() + "Filename") instead of simply Filename, and then Wt provides a means to allow you to move those files around, or start multiple instances of your application using files in different locations. Again, this mechanism is optional, and we provide it as a conventional way to access such files, but you may also choose to use relative or absolute paths in your application, or use yet another method to locate these files. If you did not configure approot specifically for your application, it defaults to an empty string, so the files will be relative to your 'current work directory'.

A docroot set to d:/dev/wdi/Bin/Debug is almost always wrong (assuming that this is your build directory containing your executable). This means that your .exe file can be downloaded though the built-in http server.

You don't specify an approot path (assuming you didn't specify it in wt_config.xml neither), so it defaults to the CWD. What is the working directory when you start service.exe? It should be d:/dev/... Alternatively, specify approot on the commandline, and then the CWD will not matter anymore to find your resources file:

service.exe --http-address=0.0.0.0 --http-port=8080 --docroot=D:\dev\wdi\Bin\Debug --approot=D:\dev\wdi\Bin\Debug

Note that approot is a new option in wt 3.1.9, and that docroot in the line above is probably still pointing to the wrong location. You can set approot also in wt_config.xml, and other connectors may allow you to set it in yet other ways.

Hope this helps,

Wim.

Thank you for your reply!

Problem solved.