Dealing with XML #108
Merged
Dealing with XML #108
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexreg
requested changes
Jan 27, 2018
docs/prepare-font.md
Outdated
|
|
||
| This document describes the correspondence between the font files we use and | ||
| data in `DefaultTexFont.xml`. The conrete approach (e.g. script files to | ||
| regenerate XML data) wasn't reproduced yet, although we were able to get nearly |
There was a problem hiding this comment.
hasn't been reproduced yet *
docs/prepare-font.md
Outdated
| ====================================================== | ||
|
|
||
| This document describes the correspondence between the font files we use and | ||
| data in `DefaultTexFont.xml`. The conrete approach (e.g. script files to |
There was a problem hiding this comment.
i.e. * (I think you mean?)
docs/prepare-font.md
Outdated
|
|
||
| Data in our XML files is often inaccurate and/or seemlingly generated from other | ||
| TTF files than the files in the repository. Be prepared for that. When in doubt, | ||
| refer to [the original tfm files][tfm] (they seem to correspond to our data |
docs/prepare-font.md
Outdated
| refer to [the original tfm files][tfm] (they seem to correspond to our data | ||
| better than the TFM files generated from our TTF files). | ||
|
|
||
| There're two helpful tool sets to work with our TTF files: |
docs/prepare-font.md
Outdated
|
|
||
| `ttf2tfm` and `tftopl` are parts of the standard TeX distribution (at least | ||
| TeX Live). | ||
| 2. It may be helpful to use [ttx][] utility to get some additional information |
docs/prepare-font.md
Outdated
| `CHARDP` corresponds to `depth`, and `CHARIC` corresponds to `italic`. Any of | ||
| them could be ommited. | ||
|
|
||
| Kerning section could also be reconstructed from the `*.tpl` file. |
There was a problem hiding this comment.
The kerning section can also be... *
docs/prepare-font.md
Outdated
|
|
||
| Kerning section could also be reconstructed from the `*.tpl` file. | ||
|
|
||
| How to know that `O 177` is the same as `code="196"`? To do that, first look |
docs/prepare-font.md
Outdated
| ``` | ||
|
|
||
| It means that `O 177` should be character `0xa8` or `168`, not `196`. The reason | ||
| for that contradiction is currently unknown. |
There was a problem hiding this comment.
I think "inconsistency" is a better word here.
|
Thanks a lot for your review, Alex! I'll fix the issues tomorrow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I finally was able to generate most of the XML data from our font files. There're still some strange contradictions, but at least now they're documented!
Next step: #107.
Closes #70.