[Insight-developers] Image writing with unicode filename impossible with MSVC

[Luis Ibanez]

Brad,

              Thanks for the feedback.

Tom,

It looks like adopting utf-cpp is our best next option.


Have you verified that this library provides all the
functionalities that we need ?

If so, we could proceed to CMake-ify it  and then to add it
to the Utilities directory.  It should be very straight forward
since it is only composed of three or four header files...

Then we could proceed to implement a class:

               itkUnicodeString

to package the functionality of the library.



Please let us know what you find.


      Thanks


           Luis


-------------------------------------------------------------------------
On Mon, Oct 19, 2009 at 11:15 AM, Brad King <brad.king at kitware.com> wrote:
> Luis Ibanez wrote:
>> Your suggestion of moving vtkUnicodeString to kwsys
>> makes a lot of sense.
>>
>> We are checking with the maintainers of kwsys, to see
>> if there are any drawbacks...
>>
>> --
>>
>> The second option:  adopting the  utf-cpp  library, also
>> looks good. the license is essentially the MIT license:
>> http://www.opensource.org/licenses/mit-license.php
>>
>> and the size of the library is just 132 Kb.
>>
>>
>> Let's see first what we hear from kwsys gurus.
>
> As the primary maintainer of KWSys I prefer to put as little
> in the library as possible.  I think using a specialized third
> party Unicode library is better, especially because its authors
> ought to know more about it than I do.
>
> -Brad
>