Private Use areas

[Peter Constable via Unicode]

This was meant to go to the list.

From: Peter Constable
Sent: Monday, August 27, 2018 12:33 PM
To: wjgo_10009 at btinternet.com; jameskasskrv at gmail.com; richard.wordingham at ntlworld.com; mark at kli.org; beckiergb at gmail.com; verdy_p at wanadoo.fr
Subject: RE: Private Use areas

That sounds like a non-conformant use of characters in the U+24xx block.


Peter

From: Unicode <unicode-bounces at unicode.org<mailto:unicode-bounces at unicode.org>> On Behalf Of William_J_G Overington via Unicode
Sent: Monday, August 27, 2018 2:00 AM
To: jameskasskrv at gmail.com<mailto:jameskasskrv at gmail.com>; richard.wordingham at ntlworld.com<mailto:richard.wordingham at ntlworld.com>; mark at kli.org<mailto:mark at kli.org>; beckiergb at gmail.com<mailto:beckiergb at gmail.com>; verdy_p at wanadoo.fr<mailto:verdy_p at wanadoo.fr>
Cc: unicode at unicode.org<mailto:unicode at unicode.org>
Subject: Re: Private Use areas

Hi

How about the following method.

In a text file that contains text that uses Private Use Area characters, start the file with a sequence of Enclosed Alphanumeric characters from regular Unicode, that sequence containing the metadata relating to those Private Use Area characters as used in their present context.

http://www.unicode.org/charts/PDF/U2460.pdf

Use circled digits U+24EA, U+2460 .. U+2469, and Circled Latin letters U+24B6 .. U+24E9.

Use U+2473 as if it were a circled space. The use of 20 to mean a space often occurs in web addresses. I know that there it is hexadecimal and here it is decimal but it has the same look of being an encoded space and so that is why I am suggesting using it.

Start the sequence with PUAINFO encoded using seven circled Latin letters and any character other than a carriage return or a line feed shows that the sequence has ended. The use of PUAINFO encoded using seven circled Latin letters at the start of the sequence is so that text using enclosed alphanumeric characters for another purpose would not become disrupted.

Then a suitable software application can read the text file and then, either automatically or after the clicking of a button, extract metadata information from the sequence of enclosed alphanumeric characters and not display the sequence of enclosed alphanumeric characters.

Maybe other circled numbers in the range 10 through to 19 would have special meanings.

This method would keep everything within plane zero.

William Overington

Monday 27 August 2018





----Original message----
From : unicode at unicode.org<mailto:unicode at unicode.org>
Date : 2018/08/21 - 23:23 (GMTDT)
To : doug at ewellic.org<mailto:doug at ewellic.org>
Cc : unicode at unicode.org<mailto:unicode at unicode.org>
Subject : Re: Private Use areas
On Tue, Aug 21, 2018 at 3:02 PM Doug Ewell via Unicode <unicode at unicode.org<mailto:unicode at unicode.org>> wrote:
Ken Whistler wrote:

> The way forward for folks who want to do this kind thing is:
>
> 1. Define a *protocol* for reliable interchange of custom character
> property information about PUA code points.

I've often thought that would be a great idea. You can't get to steps 2
and 3 without step 1. I'd gladly participate in such a project.

As would I.








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/unicode/attachments/20180827/ddf09e65/attachment.html>