[smufl-discuss] Re: JSON

[Laurent Pugin]

It sounds like a good idea, thanks. However, I would prefer to avoid
to have to do it and for now I am not sure I will actually need the
anchor points.I asked because I looked at the Gonville font (Musecore)
and I noticed that the flags (U+E240 or U+E241) are not positioned as
in Bravura. There is a space between the position x=0 and the glyph.
This means that it does not work for me when I use it. Is this type
for positioning specificities we can indicate with anchors? I can
imagine there are cases where one might want to have it, but they are
also probably many cases it should not be necessary in my opinion
(such as for the flags).

Laurent

On Sat, Dec 13, 2014 at 3:20 PM, Grzegorz Rolek <[hidden email]> wrote:

>
> On 13 Dec 2014, at 12:39, Daniel Spreadbury <[hidden email]> wrote:
>
>> Laurent wrote:
>>
>>> I work with SVG fonts and cannot see anchor information in the files I have. Can anchors be added in FontLab or FontForge and appear in the SVG font exported from them (Sorry, I am not an expert with these issues) ?
>>
>> Anchors are not exported directly in the font: they are used as metadata even within FontLab for various features like mark positioning, e.g. to align diacritics with letters when producing them via combination.
>
> FontLab aside, font editors these days usually think of, and for that matter export, such anchors as OpenType Layout data for its attachment-based glyph positioning.
>
>
>> As far as I know there's no support for features like mark positioning in SVG fonts, so I would not expect anchors to be persisted in these files: that's one of the reasons why the recommendation is to include this information in the font's JSON metadata.
>
> In non-OpenType TrueType fonts, or even OpenType fonts but with TrueType outlines, the usual practice for providing anchor-like coordinates in the font file is by standalone points placed on the glyph's canvas. Technically such points constitute separate, open contours on their own that are effectively ignored in rendering, so they provide a simple mechanism for anchor-like data within a glyph. Coordinates of such points can also be moved by TrueType hinting instructions just like the outline itself, so they are actually considered a more flexible and precise alternative to the one-size-fits-all anchors data in OpenType. The way those points are referred to is simply by their point index within the glyph overall outline data.
>
> Laurent, maybe you should try a similar technique, that is, create such standalone points and refer to them by their point index in your subsequent processing?
>
> Regards,
> Grzegorz Rolek
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>   the mailing list <[hidden email]>.
> To unsubscribe, E-mail to: <[hidden email]>
> To switch to the DIGEST mode, E-mail to <[hidden email]>
> To switch to the INDEX mode, E-mail to <[hidden email]>
> Send administrative queries to  <[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>