 | |
fonts
Dotnet Internationalization microsoft.public.dotnet.internationalization
 |
| | Thread Tools | Search this Thread | Display Modes |
#21
 
| |||
| |||
|
Re: fonts -
09-30-2005
, 08:31 PM
|
From your description, it sounds like East Asian language support may not be installed on that system. When you load Regional and Language Options from Control Panel, is the checkbox labeled 'Install files for East Asian languages' on the Languages tab checked? This should cause the SystemLink registry key to be updated with the East Asian fonts. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 12:47:01 -0700 Newsgroups: microsoft.public.dotnet.internationalization I must be missing something - there is no linking from Microsoft Sans Serif to MS UI Gothic under Windows XP English (system locale English) Andrew "Garrett McGowan[MSFT]" wrote: The linking will still work, but any Roman characters in your Japanese UI will be rendered using Microsoft Sans Serif. The Japanese characters will be rendered using MS UI Gothic (via font linking). You may already know this work-around, but you could set your forms to use the system Icon font. This defaults to the true system font, so is Tahoma on non-EA, non-CS language versions of Windows. this.Font = SystemFonts.IconTitleFont; Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 07:41:11 -0700 Newsgroups: microsoft.public.dotnet.internationalization But you're assuming the system locale has been changed to Japanese. My application supports "on-the-fly" language switching so it needs to run in Japanese, independent of the current system or user locale. Andrew "Michael (michka) Kaplan [MS]" wrote: On an XP/Server 2003 machine, the font linking chasin when you select Japanese as your default system locale and use Microsoft Sans Serif is: MSGOTHIC.TTC,MS UI Gothic gulim.ttc,gulim SimSun.TTC,SimSun mingliu.ttc,PMingLiU So clearly it will link. Michael "AndrewEames" <AndrewEames (AT) discussions (DOT) microsoft.com> wrote in message news:E6B1AC7E-75B0-48E0-AA29-3566767D9F7E (AT) microsoft (DOT) com... No that wasn't what I meant. If my application is running in Japanese under English XP, I presumably want the font to be MS UI Gothic. If I just leave the font to be the default Microsoft Sans Serif, I will not get MS UI Gothic - instead my application needs to explicitly set the font to be MS UI Gothic Andrew "Garrett McGowan[MSFT]" wrote: Yes, I think I see what you're referring to. If any UI strings are left in English on an East Asian language version of a Windows Form, the font-selection bug causes those strings to render in Microsoft Sans Serif. An English Windows XP user would expect to see those English strings rendered in Tahoma, while a Japanese Windows XP user expects to see the English strings rendered in MS UI Gothic. Instead, what you end up with is Japanese strings in MS UI Gothic and English strings in Microsoft Sans Serif. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Thu, 29 Sep 2005 14:04:13 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif may be linked to something useful under a localised OS (I haven't checked) but its not when running under English XP. If I am running my application in Japanese under English XP (with the MUI installed) , I presumably want the font to be MS UI Gothic which is not the same as Microsoft Sans Serif Andrew "Garrett McGowan[MSFT]" wrote: Andrew: You were right, I was wrong. It *should* render using Tahoma on most Windows language versions, but it does not. Add me to the list of people who would love to see this bug fixed. As to your original question of supporting East Asian languages, Microsoft Sans Serif should link appropriately to the related system fonts, without extra work on your side. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 12:08:03 -0700 Newsgroups: microsoft.public.dotnet.internationalization I dont believe this is the case - Make a form with 2 labels , one with the default font and with Tahoma and you can see they are different See also http://weblogs.asp.net/kdente/archiv...13/394499.aspx for a discussion on why this so Andrew "Garrett McGowan[MSFT]" wrote: If you leave the default font property value set to Microsoft Sans Serif, the Windows Form will automatically map to the correct system font based on the Windows language version. This means that an English language Windows Forms application automatically uses Tahoma on Windows XP. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 10:27:25 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif != Tahoma and the XP style guidelines call for the use of Tahoma under Windows XP Andrew "Garrett McGowan[MSFT]" wrote: If this is a Windows Form application, then the default font setting should cover all .NET-supported languages. Windows Forms use 'Microsoft Sans Sarif' by default, which is a logical font that maps to the appropriate system font at runtime. Is there a particular reason you are trying to set this programmatically? Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 06:40:04 -0700 Newsgroups: microsoft.public.dotnet.internationalization SYSTEM_FONT is not right either - You can't use SYSTEM_FONT from a .NET application - it claims not to be a truetype font Andrew "Mihai N." wrote: AndrewEames (AT) discussions (DOT) microsoft.com wrote in news:4A3DEB5E-A67B-4029-8DD3-FB9615C59EE8 (AT) microsoft (DOT) com: I'm pretty sure that this is not what I want - why should I want different fonts in my dialgs and non-dialogs? See Garrett's post. On my English XP machine, DEFAULT_GUI_FONT is Microsoft Sans Serif and MS Shell Dlg 2 is Tahoma. To follow the XP style Guildelines my non-dialogs should use Tahoma font too I believe You are right. It seems I am a bit behind :-) So, correction: see SYSTEM_FONT. From the doc for GetStockObject: DEFAULT_GUI_FONT = Default font for user interface objects such as menus and |
#22
| |||
| |||
|
|
I'm not sitting at such a machine right now but how could such a link possibly work. My font is Sans Serif, I'm running in English locale under Windows XP but my app could be running in any language - if MS Sans Serif is linked to MS UI Gothic then its going to be wrong for Korean - if its linked to to Gulim, its going to be wrong for Japanese - I think my app needs to explicitly call out the font Andrew "Garrett McGowan[MSFT]" wrote: From your description, it sounds like East Asian language support may not be installed on that system. When you load Regional and Language Options from Control Panel, is the checkbox labeled 'Install files for East Asian languages' on the Languages tab checked? This should cause the SystemLink registry key to be updated with the East Asian fonts. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 12:47:01 -0700 Newsgroups: microsoft.public.dotnet.internationalization I must be missing something - there is no linking from Microsoft Sans Serif to MS UI Gothic under Windows XP English (system locale English) Andrew "Garrett McGowan[MSFT]" wrote: The linking will still work, but any Roman characters in your Japanese UI will be rendered using Microsoft Sans Serif. The Japanese characters will be rendered using MS UI Gothic (via font linking). You may already know this work-around, but you could set your forms to use the system Icon font. This defaults to the true system font, so is Tahoma on non-EA, non-CS language versions of Windows. this.Font = SystemFonts.IconTitleFont; Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 07:41:11 -0700 Newsgroups: microsoft.public.dotnet.internationalization But you're assuming the system locale has been changed to Japanese. My application supports "on-the-fly" language switching so it needs to run in Japanese, independent of the current system or user locale. Andrew "Michael (michka) Kaplan [MS]" wrote: On an XP/Server 2003 machine, the font linking chasin when you select Japanese as your default system locale and use Microsoft Sans Serif is: MSGOTHIC.TTC,MS UI Gothic gulim.ttc,gulim SimSun.TTC,SimSun mingliu.ttc,PMingLiU So clearly it will link. Michael "AndrewEames" <AndrewEames (AT) discussions (DOT) microsoft.com> wrote in message news:E6B1AC7E-75B0-48E0-AA29-3566767D9F7E (AT) microsoft (DOT) com... No that wasn't what I meant. If my application is running in Japanese under English XP, I presumably want the font to be MS UI Gothic. If I just leave the font to be the default Microsoft Sans Serif, I will not get MS UI Gothic - instead my application needs to explicitly set the font to be MS UI Gothic Andrew "Garrett McGowan[MSFT]" wrote: Yes, I think I see what you're referring to. If any UI strings are left in English on an East Asian language version of a Windows Form, the font-selection bug causes those strings to render in Microsoft Sans Serif. An English Windows XP user would expect to see those English strings rendered in Tahoma, while a Japanese Windows XP user expects to see the English strings rendered in MS UI Gothic. Instead, what you end up with is Japanese strings in MS UI Gothic and English strings in Microsoft Sans Serif. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Thu, 29 Sep 2005 14:04:13 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif may be linked to something useful under a localised OS (I haven't checked) but its not when running under English XP. If I am running my application in Japanese under English XP (with the MUI installed) , I presumably want the font to be MS UI Gothic which is not the same as Microsoft Sans Serif Andrew "Garrett McGowan[MSFT]" wrote: Andrew: You were right, I was wrong. It *should* render using Tahoma on most Windows language versions, but it does not. Add me to the list of people who would love to see this bug fixed. As to your original question of supporting East Asian languages, Microsoft Sans Serif should link appropriately to the related system fonts, without extra work on your side. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 12:08:03 -0700 Newsgroups: microsoft.public.dotnet.internationalization I dont believe this is the case - Make a form with 2 labels , one with the default font and with Tahoma and you can see they are different See also http://weblogs.asp.net/kdente/archiv...13/394499.aspx for a discussion on why this so Andrew "Garrett McGowan[MSFT]" wrote: If you leave the default font property value set to Microsoft Sans Serif, the Windows Form will automatically map to the correct system font based on the Windows language version. This means that an English language Windows Forms application automatically uses Tahoma on Windows XP. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 10:27:25 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif != Tahoma and the XP style guidelines call for the use of Tahoma under Windows XP Andrew "Garrett McGowan[MSFT]" wrote: If this is a Windows Form application, then the default font setting should cover all .NET-supported languages. Windows Forms use 'Microsoft Sans Sarif' by default, which is a logical font that maps to the appropriate system font at runtime. Is there a particular reason you are trying to set this programmatically? Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 06:40:04 -0700 Newsgroups: microsoft.public.dotnet.internationalization SYSTEM_FONT is not right either - You can't use SYSTEM_FONT from a .NET application - it claims not to be a truetype font Andrew "Mihai N." wrote: AndrewEames (AT) discussions (DOT) microsoft.com wrote in news:4A3DEB5E-A67B-4029-8DD3-FB9615C59EE8 (AT) microsoft (DOT) com: I'm pretty sure that this is not what I want - why should I want different fonts in my dialgs and non-dialogs? See Garrett's post. On my English XP machine, DEFAULT_GUI_FONT is Microsoft Sans Serif and MS Shell Dlg 2 is Tahoma. To follow the XP style Guildelines my non-dialogs should use Tahoma font too I believe You are right. It seems I am a bit behind :-) So, correction: see SYSTEM_FONT. From the doc for GetStockObject: DEFAULT_GUI_FONT = Default font for user interface objects such as menus and |
#23
| |||
| |||
|
|
That is how font linkiing works, Andrew -- your system locale decides the priority order by which ideographs would be selected. If you want to explicitly have a particular language then you must explicitly choose the font you want for the language. But remember that we are talking about Microsoft Sans Serif hre, NOT MS Sans Serif. They are different! -- MichKa [Microsoft] NLS Collation/Locale/Keyboard Technical Lead Globalization Infrastructure, Fonts, and Tools Blog: http://blogs.msdn.com/michkap This posting is provided "AS IS" with no warranties, and confers no rights. "AndrewEames" <AndrewEames (AT) discussions (DOT) microsoft.com> wrote in message news:959BA9E6-850B-404B-8CE0-4D9B4FE045AA (AT) microsoft (DOT) com... I'm not sitting at such a machine right now but how could such a link possibly work. My font is Sans Serif, I'm running in English locale under Windows XP but my app could be running in any language - if MS Sans Serif is linked to MS UI Gothic then its going to be wrong for Korean - if its linked to to Gulim, its going to be wrong for Japanese - I think my app needs to explicitly call out the font Andrew "Garrett McGowan[MSFT]" wrote: From your description, it sounds like East Asian language support may not be installed on that system. When you load Regional and Language Options from Control Panel, is the checkbox labeled 'Install files for East Asian languages' on the Languages tab checked? This should cause the SystemLink registry key to be updated with the East Asian fonts. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 12:47:01 -0700 Newsgroups: microsoft.public.dotnet.internationalization I must be missing something - there is no linking from Microsoft Sans Serif to MS UI Gothic under Windows XP English (system locale English) Andrew "Garrett McGowan[MSFT]" wrote: The linking will still work, but any Roman characters in your Japanese UI will be rendered using Microsoft Sans Serif. The Japanese characters will be rendered using MS UI Gothic (via font linking). You may already know this work-around, but you could set your forms to use the system Icon font. This defaults to the true system font, so is Tahoma on non-EA, non-CS language versions of Windows. this.Font = SystemFonts.IconTitleFont; Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 07:41:11 -0700 Newsgroups: microsoft.public.dotnet.internationalization But you're assuming the system locale has been changed to Japanese. My application supports "on-the-fly" language switching so it needs to run in Japanese, independent of the current system or user locale. Andrew "Michael (michka) Kaplan [MS]" wrote: On an XP/Server 2003 machine, the font linking chasin when you select Japanese as your default system locale and use Microsoft Sans Serif is: MSGOTHIC.TTC,MS UI Gothic gulim.ttc,gulim SimSun.TTC,SimSun mingliu.ttc,PMingLiU So clearly it will link. Michael "AndrewEames" <AndrewEames (AT) discussions (DOT) microsoft.com> wrote in message news:E6B1AC7E-75B0-48E0-AA29-3566767D9F7E (AT) microsoft (DOT) com... No that wasn't what I meant. If my application is running in Japanese under English XP, I presumably want the font to be MS UI Gothic. If I just leave the font to be the default Microsoft Sans Serif, I will not get MS UI Gothic - instead my application needs to explicitly set the font to be MS UI Gothic Andrew "Garrett McGowan[MSFT]" wrote: Yes, I think I see what you're referring to. If any UI strings are left in English on an East Asian language version of a Windows Form, the font-selection bug causes those strings to render in Microsoft Sans Serif. An English Windows XP user would expect to see those English strings rendered in Tahoma, while a Japanese Windows XP user expects to see the English strings rendered in MS UI Gothic. Instead, what you end up with is Japanese strings in MS UI Gothic and English strings in Microsoft Sans Serif. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Thu, 29 Sep 2005 14:04:13 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif may be linked to something useful under a localised OS (I haven't checked) but its not when running under English XP. If I am running my application in Japanese under English XP (with the MUI installed) , I presumably want the font to be MS UI Gothic which is not the same as Microsoft Sans Serif Andrew "Garrett McGowan[MSFT]" wrote: Andrew: You were right, I was wrong. It *should* render using Tahoma on most Windows language versions, but it does not. Add me to the list of people who would love to see this bug fixed. As to your original question of supporting East Asian languages, Microsoft Sans Serif should link appropriately to the related system fonts, without extra work on your side. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 12:08:03 -0700 Newsgroups: microsoft.public.dotnet.internationalization I dont believe this is the case - Make a form with 2 labels , one with the default font and with Tahoma and you can see they are different See also http://weblogs.asp.net/kdente/archiv...13/394499.aspx for a discussion on why this so Andrew "Garrett McGowan[MSFT]" wrote: If you leave the default font property value set to Microsoft Sans Serif, the Windows Form will automatically map to the correct system font based on the Windows language version. This means that an English language Windows Forms application automatically uses Tahoma on Windows XP. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 10:27:25 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif != Tahoma and the XP style guidelines call for the use of Tahoma under Windows XP Andrew "Garrett McGowan[MSFT]" wrote: If this is a Windows Form application, then the default font setting should cover all .NET-supported languages. Windows Forms use 'Microsoft Sans Sarif' by default, which is a logical font that maps to the appropriate system font at runtime. Is there a particular reason you are trying to set this programmatically? Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified |
#24
| |||
| |||
|
|
Well yes - which is *exactly* why font linking is not the solution for localized applications that run in a locale that *isnt* the systen locale. This is why a localized application needs to explicitly call out its font on a per language basis. The Dr International article referenced is a starter on how to do this. However, my original question was how the XP look and feel gets localised - i.e. take the XP style guidelines document and for each font in there, what should the font be for every language. The Dr International article essentially describes what Tahoma should map to but what about the other fonts? Andrew "Michael (michka) Kaplan [MS]" wrote: That is how font linkiing works, Andrew -- your system locale decides the priority order by which ideographs would be selected. If you want to explicitly have a particular language then you must explicitly choose the font you want for the language. But remember that we are talking about Microsoft Sans Serif hre, NOT MS Sans Serif. They are different! -- MichKa [Microsoft] NLS Collation/Locale/Keyboard Technical Lead Globalization Infrastructure, Fonts, and Tools Blog: http://blogs.msdn.com/michkap This posting is provided "AS IS" with no warranties, and confers no rights. "AndrewEames" <AndrewEames (AT) discussions (DOT) microsoft.com> wrote in message news:959BA9E6-850B-404B-8CE0-4D9B4FE045AA (AT) microsoft (DOT) com... I'm not sitting at such a machine right now but how could such a link possibly work. My font is Sans Serif, I'm running in English locale under Windows XP but my app could be running in any language - if MS Sans Serif is linked to MS UI Gothic then its going to be wrong for Korean - if its linked to to Gulim, its going to be wrong for Japanese - I think my app needs to explicitly call out the font Andrew "Garrett McGowan[MSFT]" wrote: From your description, it sounds like East Asian language support may not be installed on that system. When you load Regional and Language Options from Control Panel, is the checkbox labeled 'Install files for East Asian languages' on the Languages tab checked? This should cause the SystemLink registry key to be updated with the East Asian fonts. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 12:47:01 -0700 Newsgroups: microsoft.public.dotnet.internationalization I must be missing something - there is no linking from Microsoft Sans Serif to MS UI Gothic under Windows XP English (system locale English) Andrew "Garrett McGowan[MSFT]" wrote: The linking will still work, but any Roman characters in your Japanese UI will be rendered using Microsoft Sans Serif. The Japanese characters will be rendered using MS UI Gothic (via font linking). You may already know this work-around, but you could set your forms to use the system Icon font. This defaults to the true system font, so is Tahoma on non-EA, non-CS language versions of Windows. this.Font = SystemFonts.IconTitleFont; Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Fri, 30 Sep 2005 07:41:11 -0700 Newsgroups: microsoft.public.dotnet.internationalization But you're assuming the system locale has been changed to Japanese. My application supports "on-the-fly" language switching so it needs to run in Japanese, independent of the current system or user locale. Andrew "Michael (michka) Kaplan [MS]" wrote: On an XP/Server 2003 machine, the font linking chasin when you select Japanese as your default system locale and use Microsoft Sans Serif is: MSGOTHIC.TTC,MS UI Gothic gulim.ttc,gulim SimSun.TTC,SimSun mingliu.ttc,PMingLiU So clearly it will link. Michael "AndrewEames" <AndrewEames (AT) discussions (DOT) microsoft.com> wrote in message news:E6B1AC7E-75B0-48E0-AA29-3566767D9F7E (AT) microsoft (DOT) com... No that wasn't what I meant. If my application is running in Japanese under English XP, I presumably want the font to be MS UI Gothic. If I just leave the font to be the default Microsoft Sans Serif, I will not get MS UI Gothic - instead my application needs to explicitly set the font to be MS UI Gothic Andrew "Garrett McGowan[MSFT]" wrote: Yes, I think I see what you're referring to. If any UI strings are left in English on an East Asian language version of a Windows Form, the font-selection bug causes those strings to render in Microsoft Sans Serif. An English Windows XP user would expect to see those English strings rendered in Tahoma, while a Japanese Windows XP user expects to see the English strings rendered in MS UI Gothic. Instead, what you end up with is Japanese strings in MS UI Gothic and English strings in Microsoft Sans Serif. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Thu, 29 Sep 2005 14:04:13 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif may be linked to something useful under a localised OS (I haven't checked) but its not when running under English XP. If I am running my application in Japanese under English XP (with the MUI installed) , I presumably want the font to be MS UI Gothic which is not the same as Microsoft Sans Serif Andrew "Garrett McGowan[MSFT]" wrote: Andrew: You were right, I was wrong. It *should* render using Tahoma on most Windows language versions, but it does not. Add me to the list of people who would love to see this bug fixed. As to your original question of supporting East Asian languages, Microsoft Sans Serif should link appropriately to the related system fonts, without extra work on your side. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 12:08:03 -0700 Newsgroups: microsoft.public.dotnet.internationalization I dont believe this is the case - Make a form with 2 labels , one with the default font and with Tahoma and you can see they are different See also http://weblogs.asp.net/kdente/archiv...13/394499.aspx for a discussion on why this so Andrew "Garrett McGowan[MSFT]" wrote: If you leave the default font property value set to Microsoft Sans Serif, the Windows Form will automatically map to the correct system font based on the Windows language version. This means that an English language Windows Forms application automatically uses Tahoma on Windows XP. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: AndrewEames (AT) discussions (DOT) microsoft.com Subject: Re: fonts Date: Wed, 28 Sep 2005 10:27:25 -0700 Newsgroups: microsoft.public.dotnet.internationalization Microsoft Sans Serif != Tahoma and the XP style guidelines call for the use of Tahoma under Windows XP Andrew "Garrett McGowan[MSFT]" wrote: If this is a Windows Form application, then the default font setting should cover all .NET-supported languages. Windows Forms use 'Microsoft Sans Sarif' by default, which is a logical font that maps to the appropriate system font at runtime. Is there a particular reason you are trying to set this programmatically? Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified |
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.