commontype-standard / commontype

Annotated OpenType Specification
Other
23 stars 1 forks source link

[wiki] CommonType Containers #17

Open twardoch opened 3 years ago

twardoch commented 3 years ago

My https://github.com/commontype-standard/commontype/wiki/CommonType-Containers article is a rehash of older material. It attempts to establish a high-level relationship between things like WOFF, OTF, TTF, as well as things like font selection, encoding, layout and rendering.

davelab6 commented 3 years ago

I'm not a fan of the GitHub wiki feature. It can suffer concurrent editing problems and even cause edits to be lost, whereas MD files inside the repo are equally web editable within GitHub itself today, plus there's stuff like www.prose.io

davelab6 commented 3 years ago

Your document is excellent though, I love it!! Establishing better community terms for concepts people bump into but don't have shared names for is great!

twardoch commented 3 years ago

I don't want to use the wiki ultimately but let's figure out a good structure of the repo first, then we'll just be doing editing in the repo

I think the wiki is nice as a drafting tool (as it does not require accepting PRs), and then the content should be moved to the proper repo when it stabilizes a bit

davelab6 commented 3 years ago

The wiki page by @simoncozens on patent status of OFF also is great.

All the fancy XML docbook stuff seems to me kind of legacy stuff, I'd like to have the aots 1.4 spec source in markdown and a simple Jekyll website builder. Then the new CTF "documentation" (per #16) should go into a clear area in the same way, and the wiki turned off

twardoch commented 3 years ago

I agree.

One of the important things to define anew is: what is a font? :) With VFs and TTCs, it's not so easy to communicate it clearly. I need to update that doc but this was my first shot a few years back, with minor edits now.

davelab6 commented 3 years ago

@simoncozens how do you want to migrate the docs off the wiki into the main repo?

simoncozens commented 3 years ago

Does it need to be in the main repo? The wiki is useful source of more general information that isn’t the file format details, and that seems OK to me.

davelab6 commented 3 years ago

I'm not a fan of the GitHub wiki feature. It can suffer concurrent editing problems and even cause edits to be lost, whereas MD files inside the repo are equally web editable within GitHub itself today, plus there's stuff like www.prose.io

Like the ms typography site, the font file format isn't the only document needed to furnish the audience with all the information they need.

I see no reason to have the wiki at all