To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=53572
------- Additional comments from [EMAIL PROTECTED] Fri Dec 2 09:15:13 -0800 2005 ------- @vg: Actually when I was working with 1.0 codeline, I was using typedef sal_uInt16 sal_Unicode; It requires huge patch for sal, but if we can limit the casts only in sal, it seems to be good. But the reality is we have many MS Windows specific modules. Many patches of "reinterpret_cast" for all of not a few MS Windows specific modules calling native unicode WINAPIs. And modification strategy for external projects should be different. During the discussion in i#29615, I tried "typedef wchar_t sal_Unicode;" and changed my policy since then simply because less patch seem to be requied. I am not quite sure which is the right way but anyways it will take some months to rewrite them all, evaluate and test all by myself. tono (Takashi Ono) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]