Boost C++ Libraries: Ticket #3744: Possibility of output of an error message on other languages (not English). https://svn.boost.org/trac10/ticket/3744 <p> For the purpose of a possibility of output of an error message on other languages (not English), I offer the following (similarly as it is made in library Qt.): </p> <ol><li>boost:: format before analysis translates string of formatting by call to static variable from a type "std:: string (*translate) (std:: string const)"; </li></ol><ol start="2"><li>All error messages in library are made only using boost:: format. </li></ol><ol start="3"><li>It is desirable to generate at library translation a file suitable for translation (For example compatible to files *.ts libraries Qt) or at least to describe all strings necessary for translation in the documentation for errors. </li></ol> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/3744 Trac 1.4.3 Steven Watanabe Fri, 11 Dec 2009 21:01:09 GMT <link>https://svn.boost.org/trac10/ticket/3744#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3744#comment:1</guid> <description> <p> What error messages are you referring to? std::exception::what() is generally only useful for debugging. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>anonymous</dc:creator> <pubDate>Sat, 12 Dec 2009 14:49:38 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/3744#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3744#comment:2</guid> <description> <p> It not absolutely so. Certainly the most part of exceptions appears at programming errors (we will not consider them). However in a number of libraries (for example: </p> <ol><li>boost:: graph (a file "read_graphviz_new.cpp") - the input file structure is broken </li><li>boost:: program_options (a file "cmdline.cpp") - the user has entered an unknown option </li><li>boost:: property_tree (a file "info_parser.hpp") not probably to open a file </li></ol><p> ) exceptions arise not because of errors of the programmer, and because of errors in input data. In this case it is desirable for user of the program to produce the message on a native language. As it to achieve with the minimum changes in libraries, and not so complicating users of library, here the purpose of my sentence. Probably it can achieve more simple resources, in this case let's realise them. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>anonymous</dc:creator> <pubDate>Mon, 07 Jun 2010 09:35:59 GMT</pubDate> <title>status, severity changed; resolution set https://svn.boost.org/trac10/ticket/3744#comment:3 https://svn.boost.org/trac10/ticket/3744#comment:3 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> <li><strong>severity</strong> <span class="trac-field-old">Optimization</span> → <span class="trac-field-new">Cosmetic</span> </li> </ul> <p> This kind of request must be sent to the Boost ML, not the trac. </p> <p> I propose to close this ticket as this is more related to a new internationalization library. </p> Ticket