Skip to content
This repository has been archived by the owner on Mar 23, 2024. It is now read-only.

Clarify: The global designspace location can affect the composite glyph... #6

Closed
PeterCon opened this issue Dec 10, 2020 · 2 comments
Closed

Comments

@PeterCon
Copy link

PeterCon commented Dec 10, 2020

The global designspace location can affect the composite glyph, but it does not need to affect the designspace location of the base glyph directly.

Is this saying that the global designspace (GDS) location can affect the composite designspace location of components?

The OT 'glyf' chapter doesn't use the term "base glyph". Do you mean the first component in the composite description? (I'm guessing No.) Or is this saying that affects from the GDS location on a component do not affect the underlying glyph outline of the component (i.e., doesn't entail any effects on other uses of that glyph outline as a component)? Or, is this saying that the GDS location can affect the underlying outline of a component and that those effects will be seen in the composite?

In saying "doesn't need", it's not clear to me if you're saying, "In some cases, X might not happen" or rather "To achieve the design goal of the proposal, it is not a requirement that..."

@justvanrossum
Copy link
Contributor

Thanks, will think about how this can be phrased better. This also relates to #1.

justvanrossum added a commit that referenced this issue Dec 14, 2020
@justvanrossum
Copy link
Contributor

I have extended the sentence to clarify that it's indeed about achieving the design goal.

I hope the "base glyph" definition in the new Terminology section addresses the other concern.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants