A
Andrea_from_GER
Dear all,
I am looking for a solution for the following problem:
BookAntiqua is replaced by MS Mincho or other Far East fonts in Title as
well as in text boxes or shapes in Powerpoint.
This happens especially when creating a deck in English on a machine with
Japanese language/regional settings,
then handing over this document to one who translates this into cyrillic.
Upon "return" the font is replaced
by a Far East font and occupies nearly the whole slide, while cyrillic in
Book Antiqua only occupies two lines.
The template itself is in use globally, title is 24pt BookAntiqua, all other
text is Arial, the language is set to English US via language id macro in
advance.
Replacing the Far East fonts with Arial unicode helps (double-byte problem
(http://www.pptfaq.com/FAQ00287.htm) )
THX a ton to Steve Rindsberg
Also the FAR EAST Marcro (to be found in the article above) helps, but we
are looking for a solution to "prevent" or "fix" this challenging problem.
Despite the fact that this problem affects only a minority of users, we are
looking for a solution...
Any ideas? Suggestions?
Your help is highly appreciated.
I am looking for a solution for the following problem:
BookAntiqua is replaced by MS Mincho or other Far East fonts in Title as
well as in text boxes or shapes in Powerpoint.
This happens especially when creating a deck in English on a machine with
Japanese language/regional settings,
then handing over this document to one who translates this into cyrillic.
Upon "return" the font is replaced
by a Far East font and occupies nearly the whole slide, while cyrillic in
Book Antiqua only occupies two lines.
The template itself is in use globally, title is 24pt BookAntiqua, all other
text is Arial, the language is set to English US via language id macro in
advance.
Replacing the Far East fonts with Arial unicode helps (double-byte problem
(http://www.pptfaq.com/FAQ00287.htm) )
THX a ton to Steve Rindsberg
Also the FAR EAST Marcro (to be found in the article above) helps, but we
are looking for a solution to "prevent" or "fix" this challenging problem.
Despite the fact that this problem affects only a minority of users, we are
looking for a solution...
Any ideas? Suggestions?
Your help is highly appreciated.