unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 7786@debbugs.gnu.org
Subject: bug#7786: 23.2; Encoding of PostScript files
Date: Wed, 13 Oct 2021 19:35:46 +0200	[thread overview]
Message-ID: <B7E074AE-3574-48D8-B176-41EDEB1EA73B@Freenet.DE> (raw)
In-Reply-To: <83r1cona9v.fsf@gnu.org>



> Am 13.10.2021 um 18:45 schrieb Eli Zaretskii <eliz@gnu.org>:
> 
>> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
>> Date: Wed, 13 Oct 2021 18:23:50 +0200
>> Cc: Eli Zaretskii <eliz@gnu.org>,
>> 7786@debbugs.gnu.org
>> 
>>>> https://en.wikipedia.org/wiki/PostScript_Latin_1_Encoding
>>>> 
>>>> It shows the Unicode codepoint for each character in the codepage.  Or
>>>> what am I missing?
>>> 
>>> Yes, that's what I suggested using as the source -- somebody would have
>>> to transcribe that into a machine readable file.
>> 
>> Is this OK and usable?
> 
> AFAICT, that's very different from the Wikipedia data.

I created the file ten years ago. Could be I missed later some standardisation by ISO… which the Wikipedia's author knew?

Could be we mix things. My encoding stands for the encoding vector of a PostScript font.

Anyway would it help you to retrieve these files?

stdenc.txt
	#  Name:             Adobe Standard Encoding to Unicode
	#  Unicode version:  2.0
	#  Table version:    0.2
	#  Date:             30 March 1999
	#  
	#  Copyright (c) 1991-1999 Unicode, Inc. All Rights reserved.
	#  
	#  This file is provided as-is by Unicode, Inc. (The Unicode Consortium). No
	#  claims are made as to fitness for any particular purpose. No warranties of
	#  any kind are expressed or implied. The recipient agrees to determine
	#  applicability of information provided. If this file has been provided on
	#  magnetic media by Unicode, Inc., the sole remedy for any claim will be
	#  exchange of defective media within 90 days of receipt.
	#  
	#  Recipient is granted the right to make copies in any form for internal
	#  distribution and to freely use the information supplied in the creation of
	#  products supporting Unicode. Unicode, Inc. specifically excludes the right
	#  to re-distribute this file directly to third parties or other organizations
	#  whether for profit or not.
	#  
	#  Format: 4 tab-delimited fields:
	#
	#    (1) The Unicode value (in hexadecimal)
	#    (2) The Adobe Standard Encoding code point (in hexadecimal)
	#    (3) # Unicode name
	#    (4) # PostScript character name
	#  
	#  General Notes:
	# 
	#    The Unicode values in this table were produced as the result of applying
	#    the algorithm described in the section "Populating a Unicode space" in the
	#    document "Unicode and Glyph Names," at
	#    http://partners.adobe.com/asn/developer/typeforum/unicodegn.html
	#    to the characters encoded in Adobe Standard Encoding. Note that some
	#    Standard Encoding characters, such as "space", are mapped to 2 Unicode
	#    values. Refer to the above document for more details.
	#
	#  Revision History:
	#
	#    [v0.2, 30 March 1999]
	#    Different algorithm to produce Unicode values (see notes above) results in
	#    some character codes being mapped to 2 Unicode values. Updated Unicode
	#    names to Unicode 2.0 names.
	#    
	#    [v0.1, 5 May 1995] First release.
	#
	#  Contact <unicode-inc@unicode.org> with any questions or comments.
	#

symbol.txt
	#
	#  Name:             Adobe Symbol Encoding to Unicode
	#  Unicode version:  2.0
	#  Table version:    0.2
	#  Date:             30 March 1999
	#  
	#  Copyright (c) 1991-1999 Unicode, Inc. All Rights reserved.
	#  
	#  This file is provided as-is by Unicode, Inc. (The Unicode Consortium). No
	#  claims are made as to fitness for any particular purpose. No warranties of
	#  any kind are expressed or implied. The recipient agrees to determine
	#  applicability of information provided. If this file has been provided on
	#  magnetic media by Unicode, Inc., the sole remedy for any claim will be
	#  exchange of defective media within 90 days of receipt.
	#  
	#  Recipient is granted the right to make copies in any form for internal
	#  distribution and to freely use the information supplied in the creation of
	#  products supporting Unicode. Unicode, Inc. specifically excludes the right
	#  to re-distribute this file directly to third parties or other organizations
	#  whether for profit or not.
	#  
	#  Format: 4 tab-delimited fields:
	#
	#    (1) The Unicode value (in hexadecimal)
	#    (2) The Symbol Encoding code point (in hexadecimal)
	#    (3) # Unicode name
	#    (4) # PostScript character name
	#  
	#  General Notes:
	# 
	#    The Unicode values in this table were produced as the result of applying
	#    the algorithm described in the section "Populating a Unicode space" in the
	#    document "Unicode and Glyph Names," at
	#    http://partners.adobe.com/asn/developer/typeforum/unicodegn.html
	#    to the characters in Symbol. Note that some characters, such as "space",
	#    are mapped to 2 Unicode values. 29 characters have assignments in the
	#    Corporate Use Subarea; these are indicated by "(CUS)" in field 4. Refer to
	#    the above document for more details.
	#
	#  Revision History:
	#
	#    [v0.2, 30 March 1999]
	#    Different algorithm to produce Unicode values (see notes above) results in
	#    some character codes being mapped to 2 Unicode values; use of Corporate
	#    Use subarea values; addition of the euro character; changed assignments of
	#    some characters such as the COPYRIGHT SIGNs and RADICAL EXTENDER. Updated
	#    Unicode names to Unicode 2.0 names.
	#
	#    [v0.1, 5 May 1995] First release.
	#
	#  Contact <unicode-inc@unicode.org> with any questions or comments.
	#

	#
	#  Name:             Adobe Zapf Dingbats Encoding to Unicode
	#  Unicode version:  2.0
	#  Table version:    0.2
	#  Date:             30 March 1999
	#  
	#  Copyright (c) 1991-1999 Unicode, Inc. All Rights reserved.
	#  
	#  This file is provided as-is by Unicode, Inc. (The Unicode Consortium). No
	#  claims are made as to fitness for any particular purpose. No warranties of
	#  any kind are expressed or implied. The recipient agrees to determine
	#  applicability of information provided. If this file has been provided on
	#  magnetic media by Unicode, Inc., the sole remedy for any claim will be
	#  exchange of defective media within 90 days of receipt.
	#  
	#  Recipient is granted the right to make copies in any form for internal
	#  distribution and to freely use the information supplied in the creation of
	#  products supporting Unicode. Unicode, Inc. specifically excludes the right
	#  to re-distribute this file directly to third parties or other organizations
	#  whether for profit or not.
	#  
	#  Format: Three tab-delimited fields:
	#
	#    (1) The Unicode value (in hexadecimal)
	#    (2) The Zapf Dingbats Encoding code point (in hexadecimal)
	#    (3) # Unicode 2.0 name
	#    (4) # PostScript character name
	#  
	#  General Notes:
	# 
	#    The Unicode values in this table were produced as the result of
	#    applying the algorithm described in the section "Populating a Unicode
	#    space" in the document "Unicode and Glyph Names," at
	#    http://partners.adobe.com/asn/developer/typeforum/unicodegn.html
	#    to the characters in Zapf Dingbats. Note that some characters, such as
	#    "space", are mapped to 2 Unicode values. 14 characters have assignments in
	#    the Corporate Use Subarea; these are indicated by "(CUS)" in field 4.
	#    Refer to the above document for more details.
	#
	#  Revision History:
	#
	#    [v0.2, 30 March 1999] Different algorithm to produce Unicode values (see
	#    notes above) results in some character codes being mapped to 2 Unicode
	#    values; use of Corporate Use subarea values; included BLACK CIRCLE and
	#    RIGHT HALF BLACK CIRCLE. Updated Unicode names to Unicode 2.0 names.
	#    
	#    [v0.1, 5 May 1995] First release.
	#
	#  Contact <unicode-inc@unicode.org> with any questions or comments.
	#

zdingbat.txt
	#
	#  Name:             Adobe Zapf Dingbats Encoding to Unicode
	#  Unicode version:  2.0
	#  Table version:    0.2
	#  Date:             30 March 1999
	#  
	#  Copyright (c) 1991-1999 Unicode, Inc. All Rights reserved.
	#  
	#  This file is provided as-is by Unicode, Inc. (The Unicode Consortium). No
	#  claims are made as to fitness for any particular purpose. No warranties of
	#  any kind are expressed or implied. The recipient agrees to determine
	#  applicability of information provided. If this file has been provided on
	#  magnetic media by Unicode, Inc., the sole remedy for any claim will be
	#  exchange of defective media within 90 days of receipt.
	#  
	#  Recipient is granted the right to make copies in any form for internal
	#  distribution and to freely use the information supplied in the creation of
	#  products supporting Unicode. Unicode, Inc. specifically excludes the right
	#  to re-distribute this file directly to third parties or other organizations
	#  whether for profit or not.
	#  
	#  Format: Three tab-delimited fields:
	#
	#    (1) The Unicode value (in hexadecimal)
	#    (2) The Zapf Dingbats Encoding code point (in hexadecimal)
	#    (3) # Unicode 2.0 name
	#    (4) # PostScript character name
	#  
	#  General Notes:
	# 
	#    The Unicode values in this table were produced as the result of
	#    applying the algorithm described in the section "Populating a Unicode
	#    space" in the document "Unicode and Glyph Names," at
	#    http://partners.adobe.com/asn/developer/typeforum/unicodegn.html
	#    to the characters in Zapf Dingbats. Note that some characters, such as
	#    "space", are mapped to 2 Unicode values. 14 characters have assignments in
	#    the Corporate Use Subarea; these are indicated by "(CUS)" in field 4.
	#    Refer to the above document for more details.
	#
	#  Revision History:
	#
	#    [v0.2, 30 March 1999] Different algorithm to produce Unicode values (see
	#    notes above) results in some character codes being mapped to 2 Unicode
	#    values; use of Corporate Use subarea values; included BLACK CIRCLE and
	#    RIGHT HALF BLACK CIRCLE. Updated Unicode names to Unicode 2.0 names.
	#    
	#    [v0.1, 5 May 1995] First release.
	#
	#  Contact <unicode-inc@unicode.org> with any questions or comments.
	#

These were just the file headers.

--
Greetings

  Pete

"To infinity and beyond!"
				– Captain Buzz Lightyear






  reply	other threads:[~2021-10-13 17:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  0:18 bug#7786: 23.2; Encoding of PostScript files Peter Dyballa
2021-01-20 18:02 ` Lars Ingebrigtsen
2021-06-02  8:39 ` Lars Ingebrigtsen
2021-06-02 16:37   ` Peter Dyballa
2021-10-13 12:49   ` Lars Ingebrigtsen
2021-10-13 13:12     ` Lars Ingebrigtsen
2021-10-13 13:51 ` Lars Ingebrigtsen
2021-10-13 15:41   ` Eli Zaretskii
2021-10-13 16:05     ` Lars Ingebrigtsen
2021-10-13 16:18       ` Eli Zaretskii
2021-10-13 16:20         ` Lars Ingebrigtsen
2021-10-13 16:23           ` Peter Dyballa
2021-10-13 16:28             ` Lars Ingebrigtsen
2021-10-13 16:43               ` Peter Dyballa
2021-10-13 16:45             ` Eli Zaretskii
2021-10-13 17:35               ` Peter Dyballa [this message]
2021-10-13 16:43           ` Eli Zaretskii
2021-10-13 18:55             ` Lars Ingebrigtsen
2021-10-13 19:05               ` Eli Zaretskii
2021-10-13 19:07               ` Peter Dyballa
2021-10-13 21:02   ` Peter Dyballa
2021-10-14  6:42     ` Eli Zaretskii
2021-10-15 12:47       ` Lars Ingebrigtsen
2021-10-15 15:59         ` Peter Dyballa
2021-10-18  7:09           ` Lars Ingebrigtsen
2021-10-18 12:25             ` Eli Zaretskii
2021-10-18 13:17               ` Lars Ingebrigtsen
2021-10-18 15:51               ` Peter Dyballa
2021-10-18 16:00                 ` Eli Zaretskii
2021-10-19  5:49                   ` Peter Dyballa
2021-10-19 11:59                     ` Eli Zaretskii
2021-10-19 13:47                       ` Lars Ingebrigtsen
2021-10-20  5:39                         ` Peter Dyballa
2021-10-20  5:45                           ` Lars Ingebrigtsen
2021-10-20  6:18                             ` Lars Ingebrigtsen
2021-10-20 16:34                             ` Peter Dyballa
2021-10-13 21:55   ` Peter Dyballa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B7E074AE-3574-48D8-B176-41EDEB1EA73B@Freenet.DE \
    --to=peter_dyballa@freenet.de \
    --cc=7786@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).