Hi!

Ralph Glasstetter wrote:

>>You can't #ifdef the locale, unfortunately, because it's chosen at run
>>time. :-(
>>
> 
> No, but I mean something like:
> 
> #ifndef __WIN32__
>   stream << doc.toString();
> #else
>   stream << doc.toCString();
> #endif
> 
> when writing the project file.

If the documentation is correct, toString() converts the internal (UCS-2
or UCS-4 encoded) copy of the string to the current locale. But in the
project file, we always want UTF-8 encoding, independent of the locale.
Therefore, toString() is wrong, no matter if you're using Linux or Windows.

[...]
>>>PS: BTW,... the "svn diff"-patch from above does (of course) NOT change
>>>back the $Id comment line with the version information... so the binary
>>>is still called Rev70... just to avoid any confusion if someone wants to
>>>try... ;-)
>>
>>It should change the $Id lines inside the source files. But that doesn't
>>affect version.h because that file contains the latest entry. To reset
>>the version string, just delete version.h and let the script re-generate
>>it.
> 
> 
> No, it does not... dvbcut.cpp still contains...
> /* $Id: dvbcut.cpp 70 2007-09-07 09:37:12Z too-tired $ */

You're right. :-(

> The patch created with "svn diff" does not contain any $Id lines, since that 
> lines are NOT different in the repository! The keywords are just replaced by 
> their appropriate values when checking out the normal way...  

Why does CVS behave differently, then?

I consider this a bug in subversion. If I say "patch this sucker down to
r69" I really mean it...

-- 
Michael "Tired" Riepe <[EMAIL PROTECTED]>
X-Tired: Each morning I get up I die a little

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DVBCUT-user mailing list
DVBCUT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dvbcut-user

Reply via email to