On Sat, 4 Oct 2003 14:48:05 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> On Sat, 4 Oct 2003 14:41:40 +0200 (CEST) Robert Vazan <[EMAIL PROTECTED]> wrote: > > RV> I don't like this "Unicode build" idea. > > It's much simpler than a mix of ANSI and Unicode inside the same program. That mix is temporary and it is very motivating to progress in rewriting. > Boundaries would include all GUI calls. The same practice can be applied to wxWindows. I understand that wxWindows is separate team and they won't cooperate with us. But we can still convert Mahogany incrementally and switch wxWindows in one moment. > All operations with wxString. And > probably more. This would be just crazy. You get the same with Unicode build. Remember we have wxChar and wxString (and wxTextFile) everywhere exactly for this reason. Mixed code would add conversion calls, but it would remove switched types in converted areas. > RV> Sure that those boundaries look ugly and total effort > RV> is higher that with one-time conversion, but it is easier to start. > > It is much higher and I don't think that adding conversion function calls is that costly. We can give them one-character codes to make them almost invisible. > I don't think that converting to Unicode is that > difficult. But then you can get errors on startup. For example, I just compiled Mahogany against wxGtk2 and it crashes while trying to display first message, complaining about fonts. > It's true that it's mostly mechanical work and not very fun but > at least once we do it, we should be ok. We could be partially OK right now. > Win9x doesn't support Unicode version of Win32 API natively. Recently, MS > released MSLY (Layer for Unicode) which emulates it by doing what you say > below. It is much better than before but it is unfortunately quite buggy. But wxWindows can do conversion internally just like that MSLY. If it doesn't, we will convert at wxWindows interface. > Mahogany unfortunately wants to work with many languages and encodings at > once. I.e. if you write your mail in Russian even under Russian version of > Windows it's not going to work [without extra effort] because Windows uses > CP1251 and most people use KOI8-R for email. But you still have to maintain all this in non-Unicode build and you have to maintain non-Unicode build while Win9x and Gtk1.2 are around. I really don't understand why Unicode application couldn't run on non-Unicode platforms. Sure that mixing languages in one document would not work, but that's just about all there is to it. Anyway, I don't care that much about internationalization, because I don't use it myself. It's just that I will have to convert code that I have recently written and I will not see any results of that work, because I am still using Gtk 1.2. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
