Thanks a lot Wolfang for your answer. I have 5 additional questions... sorry.
-----------------------------------------------------------
\placeFLOAT becomes \placerFLOAT \startplaceFLOAT becomes \debutplacerFLOAT \placerchemical becomes \placerchemical \startplacerchemical becomes \debutplacerchemical \placefigure is a combination of the element "place" (\e!place) and the variable "figure" (\v!figure) \startplacefigure is a combination of the elements "start" (\e!start) and "place" (\e!place) and the variable "figure" (\v!figure.)
So, I'm still doing something wrong, because changing the translation of "figure" in "mult-def.lua" (in the part "variables"), only affect :
1- command "\startfigure \stopfigure" 2- "figure" in "\setuppageinjection" > alternative = figure buffer... You have to provide your modified mult-def.lua file, otherwise there is no way to check what's wrong. I get another difficulty with \startitemize and \stopitemize
the translation of the variable "itemize" has no impact on the setup-fr.pdf file produced with :
context --interface=fr --global --result=setup-fr x-setups-overview.mkiv
But, I just found that if I actually use the translated commands in a test.tex file, it just works.
% interface=fr \debuttexte \debutlister \elem first \elem second \finlister \fintexte
What should I do in order to have a setup-fr.pdf file that shows the translations actually available ? Same as above, provide your translations. With the translation of the command textwidth, I can use "largeur=0.5\largeurtexte" (cool !)
But this command is not listed in setup-fr.pdf. Is there a way to add these basic commands to setup-fr.pdf ? \textwidth is the name of a dimen register and no register names are listed. Math. I get the following error :
fonts > preloading latin modern fonts (second stage) fonts > defining > font with asked name 'fichier' is not found using lookup 'file' fonts > defining > unknown font 'fichier', loading aborted
I suppose that due to the translation of "file" to "fichier". It's OK when I switch back to - setupstrings cd:file ==> file You can translate these string because they are only used in the command
- variables file ==> file Constants (\c!...) and variables (\v!...) can be changed, only
Garulfo schrieb am 26.06.2020 um 12:27: list to provide the texts which are shown in uppercase letter, e.g. NUMBER. parameters which use the form \s!... have to be english in all cases (saves memory and improves performance).
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.
Wolfgang