Definition of Values of Property Vertical_Orientation

[Asmus Freytag]

On 8/21/2022 7:20 AM, Richard Wordingham via Unicode wrote:
> I've just spent a painful time verifying the loading of the values of
> Vertical_Orientation.  After the list of codepoints and ranges in the
> comments of VerticalOrientation.txt for which the value defaults to
> Upright, is there any reason for having the ominous wording
>
> "All other code points, assigned and unassigned, that are not listed
> explicitly in the data section of this file are given the value R."
>
> Given the current (Version 14.0) and candidate (Version 15.0) data
> sections, is there any reason for not having the more reassuring
>
> "All code points, assigned and unassigned, that are not listed
> explicitly in the data section of this file are given the value R."
>
> One could then set up the default value of the property as Rotated and
> then just read in the data section as overrides, as with other files
> just defining the value of one enumeration property.  As things stand,
> loading the property values into an application involves three steps:
>
> 1) Set up the default value.
> 2) Set up the default values for the Upright regions listed in the
> comments.
> 3) Set up the explicit values from the data file.
>
> Given the current explicit data, Step 2 is redundant.
>
> Richard.

The long-term goal is to have step 1 and 2 done via parsable @missing 
directives and to remove listings of property values for non-assigned 
code points.

We have started this process for 15.0, but to fully get there may take 
another iteration or two.

At this point, any fixes that don't go towards that longer-term goals 
would be non-starters.

A./
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20220821/97ce0046/attachment.htm>