Hi, On Tuesday, 2009-03-10 13:37:23 +0100, Eike Rathke wrote:
> Medium answer: You don't need it. Given the conversions enumerated at > http://msdn.microsoft.com/en-us/library/microsoft.visualbasic.strings.strconv.aspx > there are no codepages involved. That is incomplete and misleading. The "enumeration" isn't one but a bit mask instead, and vbUnicode and vbFromUnicode are not mentioned at all, but the issue's patch attempts to implement them. > I think the implementation of the patch attached to > http://qa.openoffice.org/issues/show_bug.cgi?id=85036 is completely > wrong for the cases of VbStrConv.Wide and VbStrConv.Narrow. Sorry, I was mislead and wrong on this. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [email protected] account, which I use for mailing lists only and don't read from outside Sun. Use [email protected] Thanks.
pgpgiSyxQT2x3.pgp
Description: PGP signature
