Yes, I think I'd prefer UTF-8 as well.
Unless most of the other generators use something else or there is a
contradicting convention or preference for CMake/CPack?
I guess I'll try running some license files through some of the
generators that you listed and see what comes out.
Thank you for your input!
Nils
On 01/10/2013 04:55 PM, Eric Noulard wrote:
2013/1/10 Nils Gladitz <[email protected]>:
I wrote the WiX part and am pondering how to support extended character sets
without having to provide an extra RTF file.
Sorry I did not connect the dots.
We've got an english license text file but our company address still
contains a german umlaut.
Yes I'm french and we do have a bunch of non-ascii characters as well
(including french trema which is just like umlaut)
but we currently avoid those since none of them appear in our address :-]
I could provide an RTF but I'd prefer not to have two license files.
I think the best way to go would be to try to go for utf-8 encoding which
is relatively widespread nowadays and goes into testing for each CPack
generator which currently use CPACK_RESOURCE_FILE_LICENSE.
Reading/writing utf-8 seems doable in plain C++ without
an example (untested) here: http://utfcpp.sourceforge.net/
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
