Notes
(0003389) Brad King (developer) 2005-12-09 16:08	I'm assigning this bug to myself because I'm interested in the problem. Please note that I've not had any experience with internationalization which is one reason I'm interested. > I have added a new file, called vtkUnicode.h. This file is based on > the ATL (some copy&paste which is allowed ??.. I don't know for the > ATL). I'm not familiar with ATL. This is probably not allowed. Where is the original code? At a quick glance it looks like that code is meant to do some custom conversions based on the current locale setting. I thought windows.h provided some macros to convert ASCII strings to wide-character strings, like _("hello"). A new version of vtkUnicode.h will have to be written that uses only names with a "vtk" prefix. It also must not use code that violates any other license. The VTK copyright must be added. > There are some warnings in ProcessFwd9x.c and ProcessWin32.c. Now, > I guess these are for Win9x only and Unicode on these platforms is > not that easy. Maybe one of the developers should take another look > at this. ProcessFwd9x is for Win9x only but must be built on any platform. ProcessWin32 is used on all Windows platforms (except cygwin). Let's leave this alone until after the rest of the support has been added. > Is Win9x support really needed today ? There is no official support > from M$ anymore. Maybe there should be a poll on that ? We will not be dropping Win9x support yet. There are still ancient UNIX platforms supported too. > Also... When will there be Unicode support in CMake ? It is always > much work to make the Unicode versions. You can add a feature request to this bug tracker under the "CMake" project. Please include in the report your current procedure for using CMake with unicode. > Another thing... Which platform does not support Unicode ? So, why > isn't VTK completely in Unicode ? It would make life a bit easier > I'd say. The main reason VTK isn't completely in Unicode is that most of it was developed in the US for customers in the US. Unicode is often an afterthought for many developers in this country (see the note at the top of these comments).

(0003536) Ingo de Boer (reporter) 2006-01-10 03:16	Hi Brad, > I'm not familiar with ATL. This is probably not allowed. Where is > the original code? No, I took portions from the atlconv.h file. I don't know if it is allowed. I see some possibilities: Re-write the code (which will be actually the same, I guess) or use ATL or re-write the code which uses this class. > provided some macros to convert ASCII strings to wide-character > strings, like _("hello"). Yes, but it is not working all the time and the class is a bit neater. You can also use _T() or L() for it. Also, sometimes you have to use different functions in the code. > A new version of vtkUnicode.h will have to be written that uses only > names with a "vtk" prefix. It also must not use code that violates > any other license. The VTK copyright must be added. I know, I just wanted to make a sugesstion for that because I didn't know which direction is preferred regarding this Unicode. I already did the Unicode stuff vor 4.4, but Unicode was not regarded for these new classes. Actually it should I guess. > ProcessFwd9x is for Win9x only but must be built on any platform. > ProcessWin32 is used on all Windows platforms (except cygwin). Let's > leave this alone until after the rest of the support has been added. Ok. Win9x does not support Unicode, but it works with the so called unicows.dll > You can add a feature request to this bug tracker under the "CMake" > project. Please include in the report your current procedure for > using CMake with unicode. Well... I guess they don't wanna hear that ;-) But I'll send a request. greets Ingo

(0036807) Kitware Robot (administrator) 2016-08-12 09:54	Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page.

Issue History
Date Modified	Username	Field	Change
2011-06-16 13:11	Zack Galbreath	Category	=> (No Category)
2016-08-12 09:54	Kitware Robot	Note Added: 0036807
2016-08-12 09:54	Kitware Robot	Status	expired => closed
2016-08-12 09:54	Kitware Robot	Resolution	open => moved

Relationships