Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.postscript > #3653 > unrolled thread

PC Encoding (why some doesn't work?)

Started bynews@zzo38computer.org.invalid
First post2021-07-28 16:23 -0700
Last post2021-08-04 23:07 -0700
Articles 10 — 5 participants

Back to article view | Back to comp.lang.postscript


Contents

  PC Encoding (why some doesn't work?) news@zzo38computer.org.invalid - 2021-07-28 16:23 -0700
    Re: PC Encoding (why some doesn't work?) ken <ken@spamcop.net> - 2021-07-29 07:51 +0100
      Re: PC Encoding (why some doesn't work?) news@zzo38computer.org.invalid - 2021-07-29 09:15 -0700
        Re: PC Encoding (why some doesn't work?) rodd@panix.com (Rod Dorman) - 2021-07-29 18:44 +0000
        Re: PC Encoding (why some doesn't work?) ken <ken@spamcop.net> - 2021-07-30 07:53 +0100
          Re: PC Encoding (why some doesn't work?) news@zzo38computer.org.invalid - 2021-07-30 09:44 -0700
            Re: PC Encoding (why some doesn't work?) rodd@panix.com (Rod Dorman) - 2021-07-30 17:49 +0000
              Re: PC Encoding (why some doesn't work?) news@zzo38computer.org.invalid - 2021-07-30 13:46 -0700
                Re: PC Encoding (why some doesn't work?) John Reiser <vendor@BitWagon.com> - 2021-07-31 10:30 -0700
                Re: PC Encoding (why some doesn't work?) luser droog <luser.droog@gmail.com> - 2021-08-04 23:07 -0700

#3653 — PC Encoding (why some doesn't work?)

Fromnews@zzo38computer.org.invalid
Date2021-07-28 16:23 -0700
SubjectPC Encoding (why some doesn't work?)
Message-ID<1627514187.bystand@zzo38computer.org>
I made a file with the PC encoding:

/PCEncoding [
  %00
  /.notdef /smileface /invsmileface /heart /diamond /club /spade /bullet
  /invbullet /circle /invcircle /mars /venus /musicalnote /musicalnotedbl /sun
  %10
  /triagrt /triaglf /arrowupdn /exclamdbl /paragraph /section /filledrect /arrowupdnbse
  /arrowup /arrowdown /arrowright /arrowleft /orthogonal /arrowboth /triagup /triagdn
  %20
  /space /exclam /quotedbl /numbersign /dollar /percent /ampersand /quotesingle
  /parenleft /parenright /asterisk /plus /comma /minus /period /slash
  %30
  /zero /one /two /three /four /five /six /seven
  /eight /nine /colon /semicolon /less /equal /greater /question
  %40
  /at /A /B /C /D /E /F /G
  /H /I /J /K /L /M /N /O
  %50
  /P /Q /R /S /T /U /V /W
  /X /Y /Z /bracketleft /backslash /bracketright /asciicircum /underscore
  %60
  /grave /a /b /c /d /e /f /g
  /h /i /j /k /l /m /n /o
  %70
  /p /q /r /s /t /u /v /w
  /x /y /z /braceleft /bar /braceright /asciitilde /house
  %80
  /Ccedilla /udieresis /eacute /acircumflex /adieresis /agrave /aring /ccedilla
  /ecircumflex /edieresis /egrave /idieresis /icircumflex /igrave /Adieresis /Aring
  %90
  /Eacute /ae /AE /ocircumflex /odieresis /ograve /ucircumflex /ugrave
  /ydieresis /Odieresis /Udieresis /cent /sterling /yen /peseta /florin
  %A0
  /aacute /iacute /oacute /uacute /ntilde /Ntilde /ordfeminine /ordmasculine
  /questiondown /logicalnot /logicalnotreversed /onehalf /onequarter /exclamdown /guillemotleft /guillemotright
  %B0
  /ltshade /shade /dkshade /SF110000 /SF090000 /SF190000 /SF200000 /SF210000
  /SF220000 /SF230000 /SF240000 /SF250000 /SF260000 /SF270000 /SF280000 /SF030000
  %C0
  /SF020000 /SF070000 /SF060000 /SF080000 /SF100000 /SF050000 /SF360000 /SF370000
  /SF380000 /SF390000 /SF400000 /SF410000 /SF420000 /SF430000 /SF440000 /SF450000
  %D0
  /SF460000 /SF470000 /SF480000 /SF490000 /SF500000 /SF510000 /SF520000 /SF530000
  /SF540000 /SF040000 /SF010000 /block /dnblock /lfblock /rtblock /upblock
  %E0
  /alpha /beta /Gamma /pi /Sigma /sigma /mu /tau
  /Phi /Theta /Omega /delta /infinity /phi /element /intersection
  %F0
  /equivalence /plusminus /greaterequal /lessequal /integraltop /integralbottom /divide /approxequal
  /degree /bulletoperator /middot /radical /nsuperior /twosuperior /blacksquare /nbspace
] readonly /Encoding defineresource pop

However, some characters doesn't work:
  /venus /Omega /bulletoperator /middot /blacksquare

Why it doesn't work? Did I put it in wrong, or is it not implemented in
the font? The font I used is "NimbusMonoPS-Regular" font in Ghostscript,
which is aliased as "Courier".

-- 
Don't laugh at the moon when it is day time in France.

[toc] | [next] | [standalone]


#3654

Fromken <ken@spamcop.net>
Date2021-07-29 07:51 +0100
Message-ID<MPG.3b6c6034ac519ba59898c8@usenet.plus.net>
In reply to#3653
In article <1627514187.bystand@zzo38computer.org>, 
news@zzo38computer.org.invalid says...
 
> I made a file with the PC encoding:
...
> However, some characters doesn't work:
>   /venus /Omega /bulletoperator /middot /blacksquare
> 
> Why it doesn't work?

Have you checked the font to see if it contains glyph descriptiosn 
identified with those names ?

> Did I put it in wrong, or is it not implemented in
> the font?

Since these are unusual glyphs, almost certainly the font doesn't 
contain them.

[toc] | [prev] | [next] | [standalone]


#3655

Fromnews@zzo38computer.org.invalid
Date2021-07-29 09:15 -0700
Message-ID<1627574054.bystand@zzo38computer.org>
In reply to#3654
ken <ken@spamcop.net> wrote:
> Have you checked the font to see if it contains glyph descriptiosn 
> identified with those names ?

It look like it doesn't include these names. (All of the other glyphs I
specified in the PCEncoding are working, though.)

> Since these are unusual glyphs, almost certainly the font doesn't 
> contain them.

Would you be able to tell me then what is the proper glyph names for PC
Encoding? If they are the glyphs that this font does not include, which
font does have it, and does Ghostscript include it? (And if not, should
Ghostscript include it?)

-- 
Don't laugh at the moon when it is day time in France.

[toc] | [prev] | [next] | [standalone]


#3656

Fromrodd@panix.com (Rod Dorman)
Date2021-07-29 18:44 +0000
Message-ID<sdusth$da2$1@reader1.panix.com>
In reply to#3655
In article <1627574054.bystand@zzo38computer.org>,
 <news@zzo38computer.org.invalid> wrote:
>ken <ken@spamcop.net> wrote:
>> Have you checked the font to see if it contains glyph descriptiosn 
>> identified with those names ?
>
>It look like it doesn't include these names. (All of the other glyphs I
>specified in the PCEncoding are working, though.)
>
>> Since these are unusual glyphs, almost certainly the font doesn't 
>> contain them.
>
>Would you be able to tell me then what is the proper glyph names for PC
>Encoding? If they are the glyphs that this font does not include, which
>font does have it, and does Ghostscript include it? (And if not, should
>Ghostscript include it?)

What do you mean by "PC encoding"?

If you want to see what glyph names a font has defined look in its
.AFM (Adobe Font Metrics) file

-- 
					-- Rod --
rodd(at)polylogics(dot)com

[toc] | [prev] | [next] | [standalone]


#3657

Fromken <ken@spamcop.net>
Date2021-07-30 07:53 +0100
Message-ID<MPG.3b6db245365a45669898c9@usenet.plus.net>
In reply to#3655
In article <1627574054.bystand@zzo38computer.org>, 
news@zzo38computer.org.invalid says...

> It look like it doesn't include these names.

Well, there you go then.

> Would you be able to tell me then what is the proper glyph names for 
PC
> Encoding? 

As Rod says, what exactly do you mean by 'PC Encoding' ?


> If they are the glyphs that this font does not include, which
> font does have it,

I have no clue. If you want to use those glyphs then it's up to you to 
source a font which includes them.


> and does Ghostscript include it?

You say yourself that the font (not Ghostsceript, Ghostscript is not a 
font) does not include these.


> (And if not, should Ghostscript include it?)

Fonts are not required to include every glyph shape known to mankind, so 
no there is no reason why the fonts used by Ghostscript should include 
them.

You can, of course, use a different font.

[toc] | [prev] | [next] | [standalone]


#3658

Fromnews@zzo38computer.org.invalid
Date2021-07-30 09:44 -0700
Message-ID<1627662951.bystand@zzo38computer.org>
In reply to#3657
ken <ken@spamcop.net> wrote:
> > Would you be able to tell me then what is the proper glyph names for
> > PC Encoding?
> 
> As Rod says, what exactly do you mean by 'PC Encoding' ?

I mean the characters of IBM PC.

-- 
Don't laugh at the moon when it is day time in France.

[toc] | [prev] | [next] | [standalone]


#3659

Fromrodd@panix.com (Rod Dorman)
Date2021-07-30 17:49 +0000
Message-ID<se1e44$l49$1@reader1.panix.com>
In reply to#3658
In article <1627662951.bystand@zzo38computer.org>,
 <news@zzo38computer.org.invalid> wrote:
>ken <ken@spamcop.net> wrote:
>> > Would you be able to tell me then what is the proper glyph names for
>> > PC Encoding?
>> 
>> As Rod says, what exactly do you mean by 'PC Encoding' ?
>
>I mean the characters of IBM PC.

With which code page?

-- 
					-- Rod --
rodd(at)polylogics(dot)com

[toc] | [prev] | [next] | [standalone]


#3660

Fromnews@zzo38computer.org.invalid
Date2021-07-30 13:46 -0700
Message-ID<1627677760.bystand@zzo38computer.org>
In reply to#3659
rodd@panix.com (Rod Dorman) wrote:
> 
> In article <1627662951.bystand@zzo38computer.org>,
>  <news@zzo38computer.org.invalid> wrote:
> >ken <ken@spamcop.net> wrote:
> >> > Would you be able to tell me then what is the proper glyph names for
> >> > PC Encoding?
> >> 
> >> As Rod says, what exactly do you mean by 'PC Encoding' ?
> >
> >I mean the characters of IBM PC.
> 
> With which code page?

Code page 437.

-- 
Don't laugh at the moon when it is day time in France.

[toc] | [prev] | [next] | [standalone]


#3661

FromJohn Reiser <vendor@BitWagon.com>
Date2021-07-31 10:30 -0700
Message-ID<J7ednbuPENM-FZj8nZ2dnUU7_8zNnZ2d@giganews.com>
In reply to#3660
>>>>> Would you be able to tell me then what is the proper glyph names for
>>>>> PC Encoding?
>>>>
>>>> As Rod says, what exactly do you mean by 'PC Encoding' ?
>>>
>>> I mean the characters of IBM PC.
>>
>> With which code page?
> 
> Code page 437.

The page  https://en.wikipedia.org/wiki/Code_page_437
lists corresponding Unicode code points (numeric values, in hex.)
Pages such as  https://unicodemap.org/details/0x255D/index.html
give names, such as "Double Up and Left" for 0xBC ==> 0x255D.

[toc] | [prev] | [next] | [standalone]


#3663

Fromluser droog <luser.droog@gmail.com>
Date2021-08-04 23:07 -0700
Message-ID<a11cf374-6469-4b04-8b51-c2f81a12d3dbn@googlegroups.com>
In reply to#3660
On Friday, July 30, 2021 at 3:44:58 PM UTC-5, ne...@zzo38computer.org.invalid wrote:
> ro...@panix.com (Rod Dorman) wrote: 
> > 
> > In article <162766295...@zzo38computer.org>, 
> > <ne...@zzo38computer.org.invalid> wrote: 
> > >ken <k...@spamcop.net> wrote: 
> > >> > Would you be able to tell me then what is the proper glyph names for 
> > >> > PC Encoding? 
> > >> 
> > >> As Rod says, what exactly do you mean by 'PC Encoding' ? 
> > > 
> > >I mean the characters of IBM PC. 
> > 
> > With which code page?
> Code page 437.
> -- 
> Don't laugh at the moon when it is day time in France.

I have a Type 3 font of Code Page 437. It just uses a fixed bitmap.
http://web.archive.org/web/20160404161535/https://code.google.com/p/xpost/downloads/detail?name=cp437.ps&can=2&q=

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.postscript


csiph-web