Hi Wolfgang,

Did you manage to have a look at the previous message
Fri Jun 26 23:38:48 CEST 202023
https://mailman.ntg.nl/pipermail/ntg-context/2020/098596.html

It contains two MWE :

1/ mult-def.lua.test1_figure.diff

2/ mult-def.lua.test2_itemize.diff + test2_itemize.tex


(not about the font issue, but the two others)






Le 27/06/2020 à 12:02, Wolfgang Schuster a écrit :
Garulfo schrieb am 27.06.2020 um 00:04:
How can I translate the variable "file" into fichier, without messing with fonts (and maybe other file related functions)
There shouldn't be a problem with fonts because they use \s!file or \s!name which aren't translated (unless you made the mistake and have \c!file in your typescripts). It's possible there is a bug somewhere but you have to provide a minimal example.

My understanding:

I translated \setupbodyfont into \configurerfonteprincipale.

But I didn't specify any font in the input file.

As soon as I specified vpagella,10pt] in the input file, font messages "'fichier' is not found" disappear.

Is there an additionnal thing to do in order to enable the loading of a default math font, without any font specification, but still with translations of "file" into "fichier" ?

I'm unable to reproduce the error.

I added the "configurerfonteprincipale" to mult-def.lua and can use it in your itemize test document without problems.

It helps to have a example which produces the error and your complete mult-def.lua file.

Also helpful is to add \tracingall (or just \tracingmacros=2) before \configurerfonteprincipale to get more informations what's happening with the command.

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to