Akira TAGOH
Akira TAGOH
Hopefully the problem can be figured out now and see some comments about this issue.
Well, "merged together as one" is a problem. let's see, given that there are a string "create" can be translated. and one module may uses it as a menu item,...
Aha. is it documented somewhere? if not, would be nice to see it. thanks for that.
loading the necessary files only from memory through FcConfigParseAndLoadFromMemory() by any way? or you could have your own conf.d where contains necessary conf files from fonts and put a config...
if sandbox modifies the default config exposed by fontconfig, your concern looks valid to me otherwise you could basically use it as is. or it may depends how sandboxes manages...
@memeplex It should AFAIU. however if it contains the filesystem specific thing like . it may not work as you expected because it may be not exposed like your host...
The most problem is that fontconfig can't flatten the order of config files on multiple places. You could mount conf.d from host somewhere on flatpak but the outcome may be...
1. fonts/mono/RedHatMonoVF.ttf 2. fonts/mono/RedHatMonoVF.ttf 3. fonts/mono/RedHatMonoVF-Italic.ttf 4. fonts/mono/RedHatMonoVF-Italic.ttf
Which C++ did you use? If they support C++17, std::variant class should be available.
Oops, I forgot to make nls support optional in meson build.