[MPEG-OTSPEC] Expressing a colourful glyph in a QR code and application of such a QR code

[Vladimir Levantovsky]

Dear William,

The general scope of a font standard is to define a universally encoded
dataset that allows to transform a machine-readable sequence of codepoints
(a text string) into a human-readable sequence of rendered glyphs. From
what you're describing, it appears that the output of the process you
suggest to standardize aims to convert a text string into another
machine-readable code. So, the answer to at least one of the questions you
asked - "is it in scope for such a standardization of the format of such a
string of glyph-describing text characters to become encoded in the font
standard" - would be _no_, it is out of scope of the font format
standardization activities.

Thank you,
Vladimir


On Sat, Dec 2, 2023 at 1:23 PM William_J_G Overington <
wjgo_10009 at btinternet.com> wrote:

> Here is a first attempt at a standard for this technique, posted for
> consultation in the hope of making progress in standardization and
> application of the idea.
>
>
> Still needed, at the least, is specification of a recommendation of how
> the glyph will be accessed by an application program in the device after
> the glyph has been gathered: for example, by a Unicode code point or by a
> sequence of Unicode characters. The possibility of including a suggestion
> of a postscript name for the glyph is also desirable.
>
>
> ====
>
>
> The whole glyph, monochrome, or colourful with monochrome backup, is
> specified between { and } wavy brackets.
>
>
> Spaces and return characters are regarded as comments and may, but need
> not, be included.
>
>
> Each item is between round parentheses.
>
>
> ---
>
>
> (%,left_x, right_x, lower_y, upper_y)
>
>
> Example,
>
>
> (%, 0, 2048, -768, 2048)
>
>
> ----
>
>
> (&, 0, 0, 0, 0)
>
>
> is for monochrome, or monochrome backup for a colourful glyph.
>
>
> ----
>
>
> (*,r_value, g_value, b_value, a_value)
>
>
> Example,
>
>
> (*, 0, 255, 0, 255)
>
>
> is for a colourful glyph of one colour as part of the total colourful
> glyph.
>
>
> ----
>
>
> Each contour is a sequence of points.
>
>
> (#, x_value, y_value, 1_for_on_curve,_0 for_off_curve, ...) for as many
> points that are in the contour.
>
>
> Example,
>
>
> (#, 256, 256, 1, 256, 1792, 0, 1792, 1792, 1, 1792, 256, 1)
>
>
> ----
>
>
> An example of the string for encoding of a complete glyph in a QR code.
>
>
> {
>
> (%, 0, 2048, 0, 2048)
>
> (&, 0, 0, 0, 0)
>
> (#, 256, 256, 1, 256, 1792, 0, 1792, 1792, 1, 1792, 256, 1)
>
> (#, 1280, 1024, 1, 1536, 1024, 1, 1536, 1280, 1, 1280, 1280, 1)
>
> (*, 0, 0, 255, 255)
>
> (#, 1280, 1024, 1, 1280, 1280, 1, 1536, 1280, 1, 1536, 1024, 1)
>
> (*, 0, 255, 0, 255)
>
> (#, 256, 256, 1, 256, 1792, 0, 1792, 1792, 1, 1792, 256, 1)
>
> }
>
>
> The idea is that the glyph, perhaps displayed printed large upon a large
> sheet of white paper as an exhibit at MoMA, the Museum of Modern Art in New
> York, is a green shape with a blue square upon it, and in the lower right
> corner of the large sheet of white paper is printed a QR code that contains
> the information needed to gather sufficient details of the glyph into a
> device that has an app with a suitable font building capability such that
> the glyph would become available for use with precision in the device.
>
>
> There is accompanying the colourful glyph information, information of a
> monochrome back up of the otherwise green shape in the foreground colour
> and the otherwise blue shape expressed as a filled square of the background
> colour (or of the colour of the paper), though that glyph is not displayed
> on the printed artwork in the museum.
>
>
> William Overington
>
>
> Saturday 2 December 2023
>
>
>
> _______________________________________________
> mpeg-otspec mailing list
> mpeg-otspec at lists.aau.at
> https://lists.aau.at/mailman/listinfo/mpeg-otspec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20231204/ca7678e3/attachment.html>