Re: How about a resource string cache?
"Mihai N." <nmihai_year_2000@yahoo.com> wrote in message
news:Xns9B4DEE73B2DC4MihaiN@207.46.248.16...
But this is still string loading, the performance is the same
Goran was worried about performance.
Yes, I wasn't clear that the benefits of this technique were syntactic sugar
and not performance.
CString str(MAKEINTRESOURCE(IDS_MY_DESIRED_STR));
You can also try CString str( (LPCTSTR)IDS_MY_DESIRED_STR );
Slightly shorter.
And potentially more readable for some (not many people
know about MAKEINTRESOURCE, but most will understand a cast)
I'm not sure. If you don't know what MAKEINTRESOURCE does, you could assume
it is a function that loads the string, then initialize CString with that
string. So even though that is not exactly what happens, the assumption
that str is initialized to the stringtable contents of IDS_MY_DESIRED_STR is
in fact true.
Whereas it may not make sense to cast a UINT to an LPCTSTR (which looks like
a gratuitous cast to fix a compiler error) and expect LoadString() to
somehow be involved.
But as you say, it depends on what the reader actually knows as to which is
better. And I like the shortness of (LPCTSTR)! :-)
Although Qt has an even better way:
...
if it exists in the active translation. It truly doesn't get any easier
than that.
The idea is very popular in the Unix/GNU/Linux world, because of the
gettext
library.
And it truly doesn't get any worse than that.
With this idea the English string is the key.
This means you can only have one "Print" one "New" and so on.
It sounds like a good thing (consistency, costs savings),
but bad internationalization.
In English the same word can be verb or a subject.
("Display" "Select" "Scan")
In latin languages the translation depends on context (a button or other
"commanding" control) vs label/title (descriptive control) must be
translated differently ("Imprimer" vs "Impression" in French).
"New" depends on gender, number, case (translated as
Nuovo/Nueva/Nuevos/Nuevas in Spanish)
Then you have words that are the same in English, but mean different
things
"Scan" the disk vs "Scan" a page of paper. In most languages these
concepts
are translated differently, with completely different words.
Yes, I know context is a huge determiner in the proper translation of a
word. I'm not sure how Qt handles this. I do know their Qt Linguist tool
tracks strings on a module basis but am not sure if it merges common strings
into one, for only one translation. I'll have to check on that, thanks.
-- David