utf-16 data (e.g. inf files)

[Matthias Kupfer]

Hi folks,

due to the perpetual problems with utf-16 files I recommend to change the 
handling in the following way as long as we don't have another working 
translation system (mui) and we want to keep a win32 compatible inf file:
We should store the files in subversion as utf-8 and convert during make and 
rbuild in utf-16 (e.g. via small c-programm or new rbuild-command), so we can 
edit and make diffs in an easy way.

Comments are very welcome

Matthias

-- 
Matthias Kupfer          Telefon [phone]
Wilhelm-Firl-Straße 21   Mobil [phone]
09122 Chemnitz

[François Revol]

>   Hi folks,
>  
>  due to the perpetual problems with utf-16 files I recommend to change 
>  the 
>  handling in the following way as long as we don't have another 
>  working 
>  translation system (mui) and we want to keep a win32 compatible inf 
>  file:
>  We should store the files in subversion as utf-8 and convert during 
>  make and 
>  rbuild in utf-16 (e.g. via small c-programm or new rbuild-command), 
>  so we can 
>  edit and make diffs in an easy way. 
BeOS has xtou but I think something like iconv is more crossplatform 
and should be available on Linux and win32 as well...
UTF-8 seems definitely better as cross-platform format anyway, but I'm 
just a guest here ;)

François.

[Daniel Reimer]

Matthias Kupfer wrote:
>   Hi folks,
>
>  due to the perpetual problems with utf-16 files I recommend to change the
>  handling in the following way as long as we don't have another working
>  translation system (mui) and we want to keep a win32 compatible inf file:
>  We should store the files in subversion as utf-8 and convert during make and
>  rbuild in utf-16 (e.g. via small c-programm or new rbuild-command), so we can
>  edit and make diffs in an easy way.
>
>  Comments are very welcome
>
>  Matthias
>
>      
I like the idea. Its a good way to get infs easily editable, too.

[Aleksey Bragin]

I criticized the idea, because it adds one more preprocessing step  
(adds to the total build time), and it's a hack around SVN's problem.  
Is there a remote chance of getting [T]SVN to properly support UTF-16?

Looking forward for more opinions.

WBR,
Aleksey.

On Nov 26, 2008, at 3:36 PM, Daniel Reimer wrote:

>   Matthias Kupfer wrote:
> >   Hi folks,
> >
> >  due to the perpetual problems with utf-16 files I recommend to  
> >  change the
> >  handling in the following way as long as we don't have another  
> >  working
> >  translation system (mui) and we want to keep a win32 compatible  
> >  inf file:
> >  We should store the files in subversion as utf-8 and convert  
> >  during make and
> >  rbuild in utf-16 (e.g. via small c-programm or new rbuild- 
> >  command), so we can
> >  edit and make diffs in an easy way.
> >
> >  Comments are very welcome
> >
> >  Matthias
> >
> >  
>  I like the idea. Its a good way to get infs easily editable, too.

[Aleksey Bragin]

After talking with Matthias, he said his util will supersede the copy  
operation we have in the makefile, so should not really add that much  
of a delay to the build.

If no other way is proposed, I'm OK to go with this one then.

WBR,
Aleksey.


On Nov 26, 2008, at 8:11 PM, Aleksey Bragin wrote:

>   I criticized the idea, because it adds one more
> preprocessing step
>  (adds to the total build time), and it's a hack around SVN's problem.
>  Is there a remote chance of getting [T]SVN to properly support UTF-16?
>
>  Looking forward for more opinions.
>
>  WBR,
>  Aleksey.

[Klemens Friedl]

2008/11/26 Aleksey Bragin <aleksey(a)reactos.org>rg>:
>   I criticized the idea, because it adds one more
> preprocessing step
>  (adds to the total build time), and it's a hack around SVN's problem.
>  Is there a remote chance of getting [T]SVN to properly support UTF-16?
>
>  Looking forward for more opinions. 
If it's just an editor problem, well then I suggest to upgrade to an
editor with UTF-16 support. Even Windows Notepad supports it. On
Windows probably every native editor app does. If you are using an non
WinNT based OS, it's on your own to choose a proper editor which
supports also other unicode tranformation formats beside the infamous
UTF-8.

BR,
Klemens