Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move f-<fontfam> files to their own directory #70

Closed
vlasakm opened this issue Aug 9, 2021 · 4 comments
Closed

Move f-<fontfam> files to their own directory #70

vlasakm opened this issue Aug 9, 2021 · 4 comments

Comments

@vlasakm
Copy link
Contributor

vlasakm commented Aug 9, 2021

I know that the font family files are part of the "base", but maybe they would deserve a separate directory. There are alot of them and they are not really preloaded, but loaded on demand at runtime.

Not sure about the name, though. families or fontfamilies or fonts like in csplain? Should fams-ini.opm be moved too, as its just the index of them?

EDIT: Maybe the same thing for hisyntax?

@olsak
Copy link
Owner

olsak commented Aug 16, 2021

All mentioned files are in the TEXINPUT pool. I don't see advantages. The tree needn't to be more complicated, IMHO.

@vlasakm
Copy link
Contributor Author

vlasakm commented Aug 23, 2021

I also forgot bib-X files.

My motivation:

  • There are a lot of files in base to scroll through. Most are font files.
  • hisyntax-X, bib-X and f-X files are not strictly part of the format, they are loaded at run time and follow certain namning conventions. They are distinct, because users can create their own variants with same names without modifying the format itself.
  • There will be possibly more of these font / hisyntax / bib files.

Everything under $TEXMF/tex/optex is in TEXINPUT, so there also aren't any disadvantages.

@olsak
Copy link
Owner

olsak commented Aug 24, 2021

I dislike too bushy trees. My current directory includes testing files for OpTeX and single symlink to the base/ of OpTeX which is named base. I am doing (with Tab completion, of course):

joe base/f-lmfonts.opm
joe base/fonts-select.opm
joe base/optex.ini
grep something base/*
etc.

My work will be more complicated if there is more than single point where all TEXINPUT files for OpTeX are. This is disadvantage of your idea from my point of view.

@vlasakm
Copy link
Contributor Author

vlasakm commented Aug 24, 2021

OK, maybe a comprise with optex/base/hisyntax, etc. could be made. Otherwise feel free to close the issue, it was just an idea.

@vlasakm vlasakm closed this as completed Aug 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants