Index » PageStream Support » General » Missing characters in Symbol font |
Sign in to add a comment. | Pages: 1 |
2018-02-11 14:01:21 CT | #1 |
---|---|
T.J. Zweers From: Netherlands Registered: 2006-02-07 Posts: 331 |
Hi all, I need to have a direction how I can add the
omega character into my drawings.
That was in the old days, because nowadays PGS 5.0.5.7 and 5.0.5.8 doesn't show that symbol anymore in Windows 10. I know that it wasn't allowed to show bitmaps here, but I want to try it anyway. This is how PGS 'sees' the Windows 10 Symbol-font":
Now I have a lot of drawings containing that character, and it is a tedious job to change those by hand (if I have another similar character available). This what Windows 10 showing with the symbol-font:
A lot of characters, more than PGS shows. I've updated
the installed font folders, and I do not include System Fonts.
No avail.
Any help is welcome. Theo -- Redacteur, illustrator bij Ligfiets.net |
2018-02-11 17:12:50 CT | #2 |
---|---|
P. Marquard From: Denmark Registered: 2006-10-29 Posts: 79 |
Did a quick test. Most of my Symbol font characters are boxes just as in your picture (which did get through, btw; thank you, that made it a lot easier to understand). I am ready to believe that since the Symbol is a MS font it does not follow the standard to the letter - that would be in the true spirit of all that is MS - and thus PGS cannot read it correctly. But now I am just guessing... I tried with the Times New Roman font (Regular) and it does show a lot of characters (3675 glyphs to be precise). Among them is an Omega which look very similar to the one in your mail: (above this should be a picture) I am not sure if you can make PGS easily find and change the "wrong" omega with the "right" omega. And I now see that in my PGS a "s" followed by a "t" makes the stangest combined symbol - now, why does it do that? Greetings, Philip Takanashi Marquard On 11-02-2018 14:01, Theo Zweers
tjzwrs@gmail.com [PageStreamSupport] wrote:
|
2018-02-11 18:06:49 CT | #3 |
---|---|
T.J. Zweers From: Netherlands Registered: 2006-02-07 Posts: 331 |
Great that there is another font with
that symbol, but still a tedious job to change those characters
(and that I can show pictures, so much helpful).
That strange st is a ligature. I think ligitures are pretty new for PGS, meaning maybe since version 5.0.5.4 (or so). So, before that you, and I didn't mind this behavior. You can remove this behavior. Select all the text, and goto tab Type/Kerning/ Set Kerning... And turn Auto Ligature to Off. Now it should be okay again. Theo Op 11-2-2018 om 17:12 schreef 'P. Marquard' pmarquard@Cunning-Enterprises.com [PageStreamSupport]: Did a quick test.
-- Redacteur, illustrator bij Ligfiets.net |
2018-02-12 15:01:06 CT | #4 |
---|---|
Tim Doty From: United States Registered: 2006-02-06 Posts: 2939 |
Hi Theo, Since you aren’t using the system fonts the symbol font is going to be limited to whatever font by that name is installed in one of your configured font folders. What I noticed immediately is that your PgS dialog says “All (255 glyphs)” which strongly suggests that this is some legacy font, or that PgS is not parsing it correctly. In “the good old days” fonts used an 8-bit index into glyphs giving an available 255 characters. Modern fonts (I always use OpenType when I can) don’t have this limitation and can have thousands upon millions of glyphs. I would start by tracking down the symbol font file that is available to PgS and evaluating it. One thing that occurs to me is that PgS font handling is a bit creaky, so it is entirely possible that Win10 is “fixing” things for it as a legacy application. Or it might simply be an unwanted interaction between the PgS font handling code and that in Win10, even if Win10 isn’t explicitly trying to accommodate legacy applications. For example, in a traditional symbol font an omega might be put in the font position for ‘w’, but in a modern font that isn’t going to be the case. Rather, the glyph for omega is going to be identified by its unicode code point. A naive mapping of glyphs from a unicode font to a legacy 8-bit style font would likely do so based on codepage, and as omega isn’t in your code page it won’t show. That would explain why the numbers and punctation appear, but not the symbols. Tim Doty > On Feb 11, 2018, at 11:06 AM, Theo Zweers tjzwrs@gmail.com [PageStreamSupport] <PageStreamSupport@yahoogroups.com> wrote: |
2018-02-12 23:21:22 CT | #5 |
---|---|
T.J. Zweers From: Netherlands Registered: 2006-02-07 Posts: 331 |
Well hello Tim!
Oh, I found the omega-character. First I looked for the character in the Arial-font (which most of my text was made in), and there is one at the second row: And look how many glyphs Arial has! Still the Symbol-font has only 255, according to PGS... What I kind of strange find, is that I use characters in the first 255 glyphs in Symbol-font. So, I suppose that those characters PGS can (!) use. So, if I use (and I did) type the 'w' in Arial-font, and change the font to Symbol, I have an omega. Theo Op 12-2-2018 om 22:01 schreef Tim Doty thoromyr@mac.com [PageStreamSupport]: Hi Theo, Since you aren’t using the system fonts the symbol font is going to be limited to whatever font by that name is installed in one of your configured font folders. What I noticed immediately is that your PgS dialog says “All (255 glyphs)” which strongly suggests that this is some legacy font, or that PgS is not parsing it correctly. In “the good old days” fonts used an 8-bit index into glyphs giving an available 255 characters. Modern fonts (I always use OpenType when I can) don’t have this limitation and can have thousands upon millions of glyphs. I would start by tracking down the symbol font file that is available to PgS and evaluating it. One thing that occurs to me is that PgS font handling is a bit creaky, so it is entirely possible that Win10 is “fixing” things for it as a legacy application. Or it might simply be an unwanted interaction between the PgS font handling code and that in Win10, even if Win10 isn’t explicitly trying to accommodate legacy applications. For example, in a traditional symbol font an omega might be put in the font position for ‘w’, but in a modern font that isn’t going to be the case. Rather, the glyph for omega is going to be identified by its unicode code point. A naive mapping of glyphs from a unicode font to a legacy 8-bit style font would likely do so based on codepage, and as omega isn’t in your code page it won’t show. That would explain why the numbers and punctation appear, but not the symbols. Tim DotyOn Feb 11, 2018, at 11:06 AM, Theo Zweers tjzwrs@gmail.com [PageStreamSupport] <PageStreamSupport@yahoogroups.com> wrote: Great that there is another font with that symbol, but still a tedious job to change those characters (and that I can show pictures, so much helpful). That strange st is a ligature. I think ligitures are pretty new for PGS, meaning maybe since version 5.0.5.4 (or so). So, before that you, and I didn't mind this behavior. You can remove this behavior. Select all the text, and goto tab Type/Kerning/ Set Kerning... <dgefafklfmmhbinc.png> And turn Auto Ligature to Off. Now it should be okay again. Theo Op 11-2-2018 om 17:12 schreef 'P. Marquard' pmarquard@Cunning-Enterprises..com [PageStreamSupport]:Did a quick test. Most of my Symbol font characters are boxes just as in your picture (which did get through, btw; thank you, that made it a lot easier to understand). I am ready to believe that since the Symbol is a MS font it does not follow the standard to the letter - that would be in the true spirit of all that is MS - and thus PGS cannot read it correctly. But now I am just guessing... I tried with the Times New Roman font (Regular) and it does show a lot of characters (3675 glyphs to be precise). Among them is an Omega which look very similar to the one in your mail: <npoeifekdcdjdnoe..png> (above this should be a picture) I am not sure if you can make PGS easily find and change the "wrong" omega with the "right" omega.. And I now see that in my PGS a "s" followed by a "t" makes the stangest combined symbol - now, why does it do that? Greetings, Philip Takanashi Marquard On 11-02-2018 14:01, Theo Zweers tjzwrs@gmail.com [PageStreamSupport] wrote:Hi all, I need to have a direction how I can add the omega character into my drawings. I type the simply the character w, and change the font to Symbol. Voila: the omega, or what I use it for, the Ohm-symbol. <acpclmcmhgmglmol.png> That was in the old days, because nowadays PGS 5.0.5.7 and 5.0.5.8 doesn't show that symbol anymore in Windows 10. I know that it wasn't allowed to show bitmaps here, but I want to try it anyway.. This is how PGS 'sees' the Windows 10 Symbol-font": <bmbbelndccglnlbd.png> Now I have a lot of drawings containing that character, and it is a tedious job to change those by hand (if I have another similar character available). This what Windows 10 showing with the symbol-font: <ikaimmejkeloogel.png> A lot of characters, more than PGS shows. I've updated the installed font folders, and I do not include System Fonts. No avail. <pnljopbjiaeohmmm.png> Any help is welcome. Theo -- Redacteur, illustrator bij Ligfiets.net-- Redacteur, illustrator bij Ligfiets.net------------------------------------ Posted by: Tim Doty <thoromyr@mac.com> ------------------------------------ ------------------------------------ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/PageStreamSupport/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/PageStreamSupport/join (Yahoo! ID required) <*> To change settings via email: PageStreamSupport-digest@yahoogroups.com PageStreamSupport-fullfeatured@yahoogroups.com <*> To unsubscribe from this group, send an email to: PageStreamSupport-unsubscribe@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
-- Redacteur, illustrator bij Ligfiets.net |
2018-02-12 15:48:12 CT | #6 |
---|---|
Deron Kazmaier From: United States Registered: 2006-01-29 Posts: 4639 |
Hi Theo (and Tim and Philip), Most any large TrueType font should have that glyph. If you are just If you can find your current Symbol font that you are using, I can also Deron On 2/12/18 3:21 PM, Theo Zweers tjzwrs@gmail.com [PageStreamSupport] wrote: -- |
2018-02-14 23:15:21 CT | #7 |
---|---|
T.J. Zweers From: Netherlands Registered: 2006-02-07 Posts: 331 |
Don't need to, Deron. I did some searching, and it is 'workable' Theo Op 12-2-2018 om 23:48 schreef PageStream Support deron@pagestream.org -- |
Sign in to add a comment. | Pages: 1 |
Index » PageStream Support » General » Missing characters in Symbol font |