From: Foster T. B. <fbr...@ad...> - 2005-03-28 17:13:53
|
Yes. I'd like to make the standard character encoding inside the ASL to be UTF8. There isn't any internationalization support currently in the application, but UTF8 is the wisest choice for the internal format. Your UXTHEME work sounds very impressive! I am interested to take a look at it when you think it's ready. Blessings, Foster ----- Original Message ----- From: "Ralph Thomas" <ra...@gm...> To: "Foster T. Brereton" <fbr...@ad...> Sent: Friday, March 25, 2005 5:13 PM Subject: Re: [Adobe-source-devel] Win32: ui-core fonts and fudges > So is it okay to standardize on UTF-8 in ui-core? By this I mean that > we assume that all strings going in and coming out of ui-core are in > UTF-8. This is very easy to do on Win32 (with WideCharToMultiByte and > friends) and MacOS (CFString supports UTF-8 as an encoding). > > UTF-8 could easily be put into the Eve/Adam files (although I guess > some care would have to be taken to correctly escape "). It has the > additional advantage of containing US-ASCII without any special > characters (so existing Eve/Adam files won't create illegible GUI). > > Thanks! > Ralph > > > On Fri, 25 Mar 2005 09:14:50 -0800, Foster T. Brereton > <fbr...@ad...> wrote: >> Intriguing! Please keep us posted. >> >> A lot of the code in Win32 is from an older project. If there are newer >> and better means of managing these UI elements I'm all for it. >> >> Blessings, >> Foster >> >> On Mar 24, 2005, at 11:07p, Ralph Thomas wrote: >> >> > Hi all, >> > >> > I've been reading through the Win32 ui-core code. I have two questions: >> > >> > 1. Why is the font name hard-coded? Shouldn't DEFAULT_GUI_FONT be >> > used? >> > 2. How does i18n work? It looks like text is always in the current >> > codepage (i.e.: not UTF-X). >> > >> > Also, I've been playing with the UXTHEME bits, and am working to >> > remove the fudges. I'm planning on doing this in such a way that when >> > UXTHEME is available (i.e.: on Windows XP and 2003) it will be used to >> > look up metrics, and when it's not available the values will be >> > calculated and fudged with constants. The UXTHEME font bits can also >> > tell you about baselines inside widgets (I think -- I haven't tested >> > it yet). >> > >> > I'm quite sure that the widget metrics can change on the fly. If you >> > open Control Panel -> Accessibility -> Display Options, and enable >> > high-contrast mode then the sizes of various standard widgets change. >> > Windows does this by sending a WM_THEMECHANGED message to all windows >> > (and stock widgets know what to do, owner drawn need to capture the >> > message). >> > >> > I'll keep you updated on my UXTHEME research :). >> > >> > Thanks, >> > Ralph >> >> -- >> Foster T. Brereton <}}}>< Romans 3:21-26 >> A d o b e S o f t w a r e T e c h n o l o g y L a b >> "What 99 percent of programmers need to know is not how to build >> components but how to use them." -- Alexander Stepanov >> >> |