Hello Dave,
As you see, the naming of keywords "Bold", "Regular", "Italic" varies in
different language versions of Excel. For instance, "Bold" is translated as
"Dolk" in Hungarian, and "Gras" in French.
Suppose that a workbook is built in an language version other than English,
like French, the keywords "Gras" cannot be rendered correctly if the
workbook is opened in other language versions of Excel.
However, if the workbook is built in an English version of Excel and opened
in other language versions, the keywords can be interpreted correctly.
That is to say, the keyword &"-,Bold" or &B can always be rendered
correctly in all language versions of Excel. To test it, I created a
workbook and set the header as bold when Excel's language setting is
English. Then I switched the language setting to French and re-open the
workbook. The header is rendered as bold correctly.
Therefore, if you purpose is to programmatically add a bold header in
workbook and applies it to all language versions of Excel, we could specify
the keyword as &"-,Bold" or &B.
Besides, to detect the current language setting of Office, we could use the
following vba code:
Application.LanguageSettings.LanguageID(msoLanguageIDUI)
(
http://www.microsoft.com/globaldev/drintl/columns/004/default.mspx)
If you have any other concerns or need anything else, please feel free to
let me know.
Regards
Jialiang Ge (
[email protected], remove 'online.')
Microsoft Online Community Support
==================================================
For MSDN subscribers whose posts are left unanswered, please check this
document:
http://blogs.msdn.com/msdnts/pages/postingAlias.aspx
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express/Windows Mail, please make sure
you clear the check box "Tools/Options/Read: Get 300 headers at a time" to
see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
