From: Garulfo <garulfo@azules.eu>
To: ntg-context@ntg.nl
Subject: Translation of ConTeXt interface
Date: Fri, 26 Jun 2020 12:27:33 +0200 [thread overview]
Message-ID: <6ec90a28-dcb8-dca0-3586-918d1be04710@azules.eu> (raw)
In-Reply-To: <7b986791-73ca-4a8f-eda9-c5d4b64d83cf@gmail.com>
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...
-----------------------------------------------------------
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 ?
-----------------------------------------------------------
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 ?
-----------------------------------------------------------
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
- variables file ==> file
How can I translate the variable "file" into fichier, without messing
with fonts (and maybe other file related functions)
-----------------------------------------------------------
> Delimited command are problematic (especially when they change
> catcodes), e.g. \startluacode use \stopluacode as hard coded delimiter
> for the environment. While it is easy to create a synonym for
> \startluacode this isn't the case for \stopluacode because the
> environment always look for \stopluacode as stopper and alternative
> names are ignored.
\startsection \stopsection and \startformula \stopformula seem OK.
How can I identify the delimited commands that should not be translated
in order to avoid this issue.
-----------------------------------------------------------
Thanks again
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-26 10:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 21:42 Wiki - Proposal to update the Welcome page Garulfo
2020-05-22 22:08 ` Hans Hagen
2020-05-22 22:35 ` Aditya Mahajan
2020-05-23 16:40 ` Garulfo
2020-05-24 2:06 ` Aditya Mahajan
2020-05-24 8:53 ` Henning Hraban Ramm
2020-05-25 7:28 ` Taco Hoekwater
[not found] ` <275687af-5e3b-b548-24b3-fa00892182d5@azules.eu>
[not found] ` <20200526003645.GA893@akela.mendelu.cz>
[not found] ` <12930461-C6D9-4BB5-A181-19AF13648AE3@bittext.nl>
[not found] ` <a2e9fc59-62ca-8ea1-bf51-2b31e7ca4da1@xs4all.nl>
[not found] ` <14bec8e6-bf23-1af3-7ef6-7b1625ab946e@azules.eu>
[not found] ` <C13C5179-7B13-403A-8CBA-D6F58C3A3459@bittext.nl>
[not found] ` <2b781da3-a54f-fa17-472c-88681327d3ea@azules.eu>
[not found] ` <FBC11AAE-DB7C-4763-BB14-706FE323EC29@bittext.nl>
[not found] ` <7b986791-73ca-4a8f-eda9-c5d4b64d83cf@gmail.com>
2020-06-26 10:27 ` Garulfo [this message]
2020-06-26 12:16 ` Translation of ConTeXt interface Wolfgang Schuster
2020-06-26 21:38 ` Garulfo
2020-06-26 22:04 ` Garulfo
2020-06-27 10:02 ` Wolfgang Schuster
2020-06-27 17:00 ` Garulfo
2020-06-27 17:16 ` Wolfgang Schuster
2020-06-28 22:07 ` Garulfo
2020-06-30 21:09 ` Garulfo
2020-06-30 21:53 ` Wolfgang Schuster
2020-06-27 16:18 ` Alan Braslau
2020-06-30 21:02 ` Garulfo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ec90a28-dcb8-dca0-3586-918d1be04710@azules.eu \
--to=garulfo@azules.eu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).