Hi again, I've finished reading the documentation and I just have a question : what if I want to inject manually the content of the translation/dictionary files in the generator instead of using the add path functions? Looking at the interface of boost::locale::generator class I don't see a way to do this other than having a "real filesystem" set of dictionary files. For example, let's say that in my project I'm using some kind of file-system virtualization library like PhysicsFS( http://icculus.org/physfs/ ). My translation files are zipped together (with other files) and this library makes it easy to manipulate them without having to bother about compression. I explicitely dont' want to use real filesystem and I can only read the content of files using the PhyscsFS file reading function, getting raw bytes. In this case I need a way to inject those raw bytes inside boost::locale as dictionary files content. Is there already a way to do this or do you recommand another way to manage this kind of case? Using some kind of real filesystem cache directory would work I guess but it's far from ideal. Joël Lamotte On Fri, Sep 10, 2010 at 15:46, Klaim <mjklaim@gmail.com> wrote:
Hi,
I'm reading the tutorial and I noticed this line :
This technique was adopted by Boost.Locale library in order to provide powerful and correct localization. However instead of using standard and very limited standard library C++ facets it created its own facets that use ICU under the hood in order to make much powerful.
As now there are several possible backends, it might be good to change this sentence?
Joël Lamotte.
On Fri, Sep 10, 2010 at 12:19, Artyom <artyomtnk@yahoo.com> wrote:
Hello All,
Announcement ============
I want to announce a preview of the third version of Boost.Locale:
Tutorial: http://cppcms.sourceforge.net/boost_locale/html/tutorial.html Reference: http://cppcms.sourceforge.net/boost_locale/html/index.html Downloads: https://sourceforge.net/projects/cppcms/files/boost_locale/
There are following significant changes:
- Implemented multiple localization backends: - icu - the default and recommended backend, based on ICU library - std - based on C++ standard library localizations support, - posix - based on POSIX 2008 API (newlocale, strftime_l,...) - winapi - based on Windows API functions - Significantly simplified locale generation. - Improvements in UTF-8 handling by ICU where possible - Thread safety fixes when using ICU library - Fixed std::codecvt facet support to handle UTF-16 instead of UCS-2 only. - Removed support of compilers missing wide character support, gcc-3.4 on windows is not supported any more, latest gcc-4.x required with support of wide streams and strings, for example gcc-4.5
Tested Platforms:
- Compilers: GCC (3.4, 4.2, 4.3, 4.5, 4.5/c++0x), Intel 11.0, MSVC 2008, SunStudio/stlport - Operating Systems: Linux, FreeBSD, OpenSolaris, Windows XP, Cygwin 1.7, (TODO Mac OS X) - ICU version: 3.6 to 4.4
Request To Site managers =========================
Please, update download link
Review ======
Is there anybody who wants to volunteer to be a review manager?
Artyom
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost