On Tuesday 01 November 2005 07:39 am, DM Smith wrote:
C++ does not support internationalization or localization. It is an
afterthought at best.
From the design point of view of a language, i18n should be an after thought
unless you have built in strings (and even in java they're a class) with
gettext is portable to Windows, I have done it.
If anyone wants I can send the .NET sources.
Also 'iconv' is ported to Windows, so charset translation
doesn not need to be done in SWORD. Again I have the .NET
files if they would help.
David Blue wrote:
On Tuesday 01 November 2005 07:39 am,
I cut my teeth on C++, as a teacher's aide to it and other OO languages
at the University of Pittsburgh. In the early days, I compiled C++ 1.0,
2.0 and 3.0 for various unix architectures and found and fixed bugs in
these implementations. In those early days I also wrote a significant
set of
Chris Umphress wrote:
On 10/31/05, Yiguang Hu [EMAIL PROTECTED] wrote:
About the encoding/book names. I am just wondering why
the standard java resource bundle is not used ?
For encoding, UTF-8 should be able to cover all the
languages. I knew it covers MBCS like Japanese,
Chinese
On 11/1/05, DM Smith [EMAIL PROTECTED] wrote:
Perhaps not everyone uses Java ;-)
So true. However, Java's resource bundle can be thought of as a design
pattern. Its basic design is worthy of consideration for any language. C++
does not support internationalization or localization. It is an
C++ can handle UTF-8 perfectly (and by default)
when used with QT liberary
It is cross platfrom C++ liberary
here is screenshot to it under windows
http://www.trolltech.com/images/screenshots/qt_vs_integration.png
--- Chris Umphress [EMAIL PROTECTED] wrote:
On 11/1/05, DM Smith [EMAIL
On Tuesday 01 November 2005 07:39 am, DM Smith wrote:
C++ does not support internationalization or localization. It is an
afterthought at best.
From the design point of view of a language, i18n should be an after thought
unless you have built in strings (and even in java they're a class) with
On 11/1/05, David Blue (Mailing List Addy) [EMAIL PROTECTED] wrote:
From the design point of view of a language, i18n should be an after thought
unless you have built in strings (and even in java they're a class) with the
exception of making sure your character types are able to hold Unicode
About the encoding/book names. I am just wondering why
the standard java resource bundle is not used ?
For encoding, UTF-8 should be able to cover all the
languages. I knew it covers MBCS like Japanese,
Chinese and Korean (Usually KJC for short) well. It
should not be a issue with any of the
On 10/31/05, Yiguang Hu [EMAIL PROTECTED] wrote:
About the encoding/book names. I am just wondering why
the standard java resource bundle is not used ?
For encoding, UTF-8 should be able to cover all the
languages. I knew it covers MBCS like Japanese,
Chinese and Korean (Usually KJC for
10 matches
Mail list logo
