From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: French interface
Date: Thu, 25 Jun 2020 22:00:04 +0200 [thread overview]
Message-ID: <d057677b-5a78-f183-ef94-0b7c3203c22e@gmail.com> (raw)
In-Reply-To: <d2b91d7c-331f-d74f-3592-ed1d43536680@azules.eu>
Garulfo schrieb am 25.06.2020 um 21:34:
> Hi,
>
> If I understand, the translation file mult-def.lua provides 5 families
> for translations:
> 1- commands
> 2- constants
> 3- variables
> 4- elements (prefix or suffix of commands) like
> - \completeREGISTER and \completeindex
> ^^^^^^^^ ^^^^^^^^
> - \startmakeup and \stopmakeup
> ^^^^^^ ^^^^^^
> 5- setupstrings, to describe the syntaxe and the type of the arguments
>
>
> 1/ I don't understand how to impact, for example, FLOAT and chemical in:
>
> \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.)
> 2/ I don't understand the following
>
> RUN OK:
>
> % interface=fr
> \debuttexte
> \debutsection[titre=test] This is a test \finsection
> \codelua{context("Foo Bar 1")}
> \fintexte
\ctxlua?
> % interface=fr
> \debuttexte
> \debutsection[titre=test] This is a test \finsection
> \debutcodelua context("Foo Bar 2") \fincodelua
> \fintexte
>
> with:
> tex error > error not related to input file:
> tex error > tex: ?
> tex error > lua: ?
> tex error > mps: -
> mtx-context | fatal error: return code: 256
>
>
> I suppose that some complementary modifications may be required with
> \start \stop and lua
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.
There are ways to work around this (e.g. \startfootnote) but for the
english interface they aren't needed in most cases.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-25 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 3:26 Filter module for R Fabrice L
2020-06-15 5:45 ` Aditya Mahajan
2020-06-15 6:04 ` Aditya Mahajan
2020-06-15 6:24 ` Aditya Mahajan
[not found] ` <82287b24-d781-808f-f96b-675f56224bb6@azules.eu>
2020-06-24 21:01 ` French interface - previous message = wrong title Garulfo
2020-06-24 21:35 ` Hans Hagen
2020-06-25 19:34 ` French interface Garulfo
2020-06-25 20:00 ` Wolfgang Schuster [this message]
2020-06-15 17:33 ` Filter module for R Fabrice L
2020-06-15 18:06 ` Aditya Mahajan
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=d057677b-5a78-f183-ef94-0b7c3203c22e@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--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).