-
Notifications
You must be signed in to change notification settings - Fork 91
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
[MiKTeX Portable] fontconfig configs use full path #17
Comments
The fontconfig files should be regenerated if you start the MiKTeX task bar icon. |
You mean "Refresh FNDB" button in MiKTeX Options? |
No, I mean the taskbar icon which you get when you run |
Seems, we talk about the same thing - "MiKTeX Options" is accessible from task bar icon contex menu.
As you can see its does not contain miktex-taskbar-icon.exe... |
Could you provide short description what is miktex-taskbar-icon attend to do? |
On startup the task-bar icon program runs this command:
This will refresh the fontconfig configuration files. I would recommend that you add this command tour your custom batch file. |
Thank you for your explanations. |
Currently, fonts.conf and localfonts.conf use full path to directories which contains fonts.
For example, my copy of localfonts.conf:
I use xetex, xetex uses fontconfig for ttf/otf font support. There is no problem until path is not changed, but it's not always true for usb flash drives. Often usb sticks get different drive letter, so full path generated when you update MiKTeX on one machine are not valid for another.
Thus leads for compiling warnings and errors.
Here is "magic" enviroment variables are valid for windows fontconfig build: LOCAL_APPDATA_FONTCONFIG_CACHE, WINDOWSTEMPDIR_FONTCONFIG_CACHE, WINDOWSFONTDIR, FONTCONFIG_FILE but seems they are useless for portable purpose.
I'm not sure, we can use relative path (relative to current directory with configs or something else?) in configs.
The text was updated successfully, but these errors were encountered: