Font acdess (again)
Gary W. Shanafelt
While I'm at it, back on January of 2004 I reported WP10 switching
characters. It still does, even with service pack 4. I checked, in
fact, and it does this for no less than nine characters, mapped at 166,
168, 173, 175, 176, 180, 181, 183, and 184. Try displaying the icons in
a font like Webdings and you get diacritics for these characters
instead. But they all display properly using MS Word or even MS
Wordpad. The newest version of WP Office, WP12, still has this bug.
Could someone try reporting it again? People aren't going to want to
use a word processor that fails to allow them to use all the characters
in a font... and this worked fine in my old WP8; it is a bug that has
crept in since then.
--
Gary W. Shanafelt
http://cs1.mcm.edu/~gshan
Charles Rossiter
Gary,
This has been reported for WPWin12, and earlier.
Instead of using Alt+0166 (as example), have you tried Ctrl+W 12,166?
Or vice versa?
--
Charles Rossiter
(South Africa)
Volunteer C_Tech
{Please reply to group only}
Gary W. Shanafelt
Ctrl+W 12,166 actually works. But it is not very useful, since the character that is displayed at 12,166 is not the actual character in the font but, rather, the character that WP10 wants to switch with it. The display characters appear to be in Arial regardless of what font has been chosen. So, to use this, you have to memorize all the characters being switched and know that, in the case of this particular font, a | (12,166) is actually going to appear as something different.
I have about 13 fonts with characters I use in these "switch" positions, so I'm simply using a font editor to reassign the characters that I want to different codes. In the process of doing this, I discovered another interesting feature (read: another bug, I assume). If you type a left guillemot («), which is used in French instead of a left quotation mark, you don't just get the guillemot; WP10 also gives you a space after it. This happens both with typing the code directly from the numeric keypad (ALT 0173) or when using CTRL W 4,9. But it doesn't happen with the right guillomot (»). That means if I were to type any extensive text in French, I'd have to go back and manually take out all the extra spaces to space it properly. Luckily, I type more German than French... but I'm again irritated at these bugs that have crept in since WP8 and that no one seems to be able to get rid of again.
In fact, I was about ready to scrap WP10 and go back to my old WP8 which worked great (except that it tends to crash with Win XP), until with your help I got the WP10 PDF feature working (well, almost working: I have some fonts that print fine but crash the PDF generator... I think the characters are too wide and so I need to track down the Acrobat 4 font specifications). You'll remember from my earlier messages here that I already had to convert my GIF clip art, which worked fine with WP8, to PNG format so I could raise their resolution from 72 to 300 to make them work with WP10 (the images were too big at 72 dpi), and now I'm converting TrueType fonts. It seems to me the first task of a word processor should be to maintain compatibility with standard font and graphics formats, not force users to change the formats to maintain compatibility with it. But enough of my soapbox. I've done some software debugging for people, and within days of reporting bugs got new versions with the problems corrected. With Corel, bug reports seem to disappear into thin air. Pass these on, and maybe we'll get lucky for ver. 12.
Charles Rossiter
WPWin11 and WPWin12 do correctly show "Current font symbols" for
character set 12. You can select a font, such as Comic Sans, and see
all the characters available in that font (within code page 1252).
On the need to memorize: there is a 1:1 relation between the character
set 12 in WPWin, and the Alt+ combination. Ctrl+W 12,166 matches
Alt+0166, for example -- except that the Alt key version selects the
character from the WP specific sets, not from the current font -- this
has been escalated to Corel.
The « problem is or is not a bug depending on the language being used.
« followed by a space is correct for French. There have been several
posts about this in the last few days. I have posted a macro which
removes the space, and which can be assigned to a keystroke.
--