Hello,
I try to build a graphical editor for musical pieces. For this I need to show some according fonts like maestro or engraver. I have also downloaded a small fontmanager from [hidden email] (N. Wayne Parrott) to learn how to handle fonts. This tool just tries to show a text string, just like I would handle it. But every time I use a symbolic font like the ones mentioned above or wingdings, the characters are all shown as black rectangles. The normal fonts that have normal letters are shown as expected. I have also tried to import the parcel AllEncodings for Unicode support, but this did not help. What can I do to make this work? Many thanks in advance Richard Zillmann _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Richard Zillmann wrote:
> But every time I use a symbolic font like the ones mentioned above or > wingdings, the characters are all shown as black rectangles. > The normal fonts that have normal letters are shown as expected. If you use normal characters ($a etc.) in your strings, they won't show up. You need to add some large number (16rE000) to them to get them to show up as they do in Word when you press 'a' etc. The following snippet will copy to the clipboard a string which will show all the Wingdings characters, when displayed in VW with Wingdings. str := (String new: 1000) writeStream. 16rE000 to: 16rE0FF do: [:val | str nextPut: (Character value: val)]. ParagraphEditor currentSelection: str contents I'm not sure whether this is a bug. Interestingly, VW has a 'dingbat' encoder that uses values 16rE000-E0FF, but is not using it for Wingdings (it uses the default Windows encoder instead). Steve _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
I think it's a bug, and fixed in 7.7. At least in 7.7, under
Windows XP, if I create a text style and assign its font as Wingdings,
then create a canvas with that style assigned to an input field, open it
and type in it, I get wingdings appearing.
At 06:39 AM 2009-12-14, Steven Kelly wrote: Richard Zillmann wrote: --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Great!
I can see the glyphs now. I think I can use them now. Thank you very much! Richard Alan Knight schrieb: > I think it's a bug, and fixed in 7.7. At least in 7.7, under Windows XP, if I create a text style and assign its font as Wingdings, then create a canvas with that style assigned to an input field, open it and type in it, I get wingdings appearing. > > At 06:39 AM 2009-12-14, Steven Kelly wrote: > >> Richard Zillmann wrote: >> >>> But every time I use a symbolic font like the ones mentioned above or >>> wingdings, the characters are all shown as black rectangles. >>> The normal fonts that have normal letters are shown as expected. >>> >> If you use normal characters ($a etc.) in your strings, they won't show >> up. You need to add some large number (16rE000) to them to get them to >> show up as they do in Word when you press 'a' etc. The following snippet >> will copy to the clipboard a string which will show all the Wingdings >> characters, when displayed in VW with Wingdings. >> >> str := (String new: 1000) writeStream. >> 16rE000 to: 16rE0FF do: [:val | >> str nextPut: (Character value: val)]. >> ParagraphEditor currentSelection: str contents >> >> I'm not sure whether this is a bug. Interestingly, VW has a 'dingbat' >> encoder that uses values 16rE000-E0FF, but is not using it for Wingdings >> (it uses the default Windows encoder instead). >> >> Steve >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> > > -- > Alan Knight [|], Engineering Manager, Cincom Smalltalk > [hidden email] > [hidden email] > http://www.cincom.com/smalltalk > > > ------------------------------------------------------------------------ > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hello,
unfortunately I still have a problem with the glyphs of symbolic fonts. I use the workaround described some days ago (see down on page). When I try to get a glyph mit number > 126, it fails. I create the strings now as follows: -------------------------------- composedTextNumber: anInt "this is a workaround for a VisualWorks bug. Shall be corrected in VW 7.7" | text | text := Text fromString: ( String with: ( Character value: 16rE000 + anInt )). ^ ComposedText withText: text style: self textStyleForNotes ---------------------------------- and it works fine for integers <= 126. But when I take bigger integers, e.g. n=130, it gives me the symbol for number n + 70! I have no idea, how I could get the missing ones ( and I need them really). I hope there is also some workaround. If not, I am rather helpless. Many thanks in advance Richard Zillmann --------------------------------------------------------------------------------------- Richard Zillmann schrieb: > Great! > > I can see the glyphs now. I think I can use them now. > Thank you very much! > > Richard > > > Alan Knight schrieb: > >> I think it's a bug, and fixed in 7.7. At least in 7.7, under Windows XP, if I create a text style and assign its font as Wingdings, then create a canvas with that style assigned to an input field, open it and type in it, I get wingdings appearing. >> >> At 06:39 AM 2009-12-14, Steven Kelly wrote: >> >> >>> Richard Zillmann wrote: >>> >>> >>>> But every time I use a symbolic font like the ones mentioned above or >>>> wingdings, the characters are all shown as black rectangles. >>>> The normal fonts that have normal letters are shown as expected. >>>> >>>> >>> If you use normal characters ($a etc.) in your strings, they won't show >>> up. You need to add some large number (16rE000) to them to get them to >>> show up as they do in Word when you press 'a' etc. The following snippet >>> will copy to the clipboard a string which will show all the Wingdings >>> characters, when displayed in VW with Wingdings. >>> >>> str := (String new: 1000) writeStream. >>> 16rE000 to: 16rE0FF do: [:val | >>> str nextPut: (Character value: val)]. >>> ParagraphEditor currentSelection: str contents >>> >>> I'm not sure whether this is a bug. Interestingly, VW has a 'dingbat' >>> encoder that uses values 16rE000-E0FF, but is not using it for Wingdings >>> (it uses the default Windows encoder instead). >>> >>> Steve >>> >>> _______________________________________________ >>> vwnc mailing list >>> [hidden email] >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>> >>> >> -- >> Alan Knight [|], Engineering Manager, Cincom Smalltalk >> [hidden email] >> [hidden email] >> http://www.cincom.com/smalltalk >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> >> > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Sorry for the confusion!
I just took a closer look at it and found, that Visualworks just shows the glyphs in another order than my other font viewer, but all of them seem to be there. I do not know, which is the correct order, but anyhow, this is ok for me. Many thanks for your patience. Richard Zillmann Richard Zillmann schrieb: > Hello, > > unfortunately I still have a problem with the glyphs of symbolic fonts. > > I use the workaround described some days ago (see down on page). > When I try to get a glyph mit number > 126, it fails. > > I create the strings now as follows: > -------------------------------- > composedTextNumber: anInt > "this is a workaround for a VisualWorks bug. Shall be corrected in > VW 7.7" > | text | > text := Text fromString: ( String with: ( Character value: 16rE000 + > anInt )). > ^ ComposedText withText: text style: self textStyleForNotes > ---------------------------------- > > and it works fine for integers <= 126. > But when I take bigger integers, e.g. n=130, it gives me the symbol for > number n + 70! > I have no idea, how I could get the missing ones ( and I need them really). > > I hope there is also some workaround. If not, I am rather helpless. > Many thanks in advance > > Richard Zillmann > > --------------------------------------------------------------------------------------- > > Richard Zillmann schrieb: > >> Great! >> >> I can see the glyphs now. I think I can use them now. >> Thank you very much! >> >> Richard >> >> >> Alan Knight schrieb: >> >> >>> I think it's a bug, and fixed in 7.7. At least in 7.7, under Windows XP, if I create a text style and assign its font as Wingdings, then create a canvas with that style assigned to an input field, open it and type in it, I get wingdings appearing. >>> >>> At 06:39 AM 2009-12-14, Steven Kelly wrote: >>> >>> >>> >>>> Richard Zillmann wrote: >>>> >>>> >>>> >>>>> But every time I use a symbolic font like the ones mentioned above or >>>>> wingdings, the characters are all shown as black rectangles. >>>>> The normal fonts that have normal letters are shown as expected. >>>>> >>>>> >>>>> >>>> If you use normal characters ($a etc.) in your strings, they won't show >>>> up. You need to add some large number (16rE000) to them to get them to >>>> show up as they do in Word when you press 'a' etc. The following snippet >>>> will copy to the clipboard a string which will show all the Wingdings >>>> characters, when displayed in VW with Wingdings. >>>> >>>> str := (String new: 1000) writeStream. >>>> 16rE000 to: 16rE0FF do: [:val | >>>> str nextPut: (Character value: val)]. >>>> ParagraphEditor currentSelection: str contents >>>> >>>> I'm not sure whether this is a bug. Interestingly, VW has a 'dingbat' >>>> encoder that uses values 16rE000-E0FF, but is not using it for Wingdings >>>> (it uses the default Windows encoder instead). >>>> >>>> Steve >>>> >>>> _______________________________________________ >>>> vwnc mailing list >>>> [hidden email] >>>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>>> >>>> >>>> >>> -- >>> Alan Knight [|], Engineering Manager, Cincom Smalltalk >>> [hidden email] >>> [hidden email] >>> http://www.cincom.com/smalltalk >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> vwnc mailing list >>> [hidden email] >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >>> >>> >>> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> >> >> >> > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |