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
2013/1/10 Nils Gladitz :
> 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 fren
I wrote the WiX part and am pondering how to support extended character
sets without having to provide an extra RTF file.
We've got an english license text file but our company address still
contains a german umlaut.
I could provide an RTF but I'd prefer not to have two license files.
Nils
O
2013/1/10 Nils Gladitz :
> Is a license text file pointed to by CPACK_RESOURCE_FILE_LICENSE expected to
> have a specific encoding (ASCII, Latin1, UTF-8, ...)?
I don't know but I bet that some encoding may be accepted by some
CPack generator
and poorly handled by others.
CPACK_RESOURCE_FILE_LICEN
Is a license text file pointed to by CPACK_RESOURCE_FILE_LICENSE
expected to have a specific encoding (ASCII, Latin1, UTF-8, ...)?
Nils
--
Nils Gladitz, B.Sc.
DICOM, Konnektivität und Entwicklung
Scivis wissenschaftliche Bildverarbeitung GmbH
Bertha-von-Suttner-Str. 5
D-37085 Göttingen
GERMANY
