From: Garulfo <garulfo@azules.eu>
To: Alan Braslau <braslau.list@comcast.net>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Translation of ConTeXt interface
Date: Tue, 30 Jun 2020 23:02:02 +0200 [thread overview]
Message-ID: <d5a5c9d4-0c48-0aea-50b9-bed955650935@azules.eu> (raw)
In-Reply-To: <73fc6b1e-830c-6358-1023-3996fd86ec89@comcast.net>
Hi Alan,
i will not forget your remark, I don't remember why I get to such a
translation. Maybe after working on translation and consistency between
these ~2000 keywords...
For "corps" and "fonte", it will be easy to change (there is not a lot
of tags)
If you agree, when I will have something "working", I will submit it to
you, in order to get your feedback (just a 10 to 15 minutes overview can
enable to catch the major issues)
Le 27/06/2020 à 18:18, Alan Braslau a écrit :
> fonte ? (police)
> principale ? (corps)
> ...
>
> Alan
>
> On 26/06/20 16:04, Garulfo wrote:
>>
>>>> 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 list to provide the texts which are shown in uppercase
>>> letter, e.g. NUMBER.
>>>> - variables file ==> file
>>> Constants (\c!...) and variables (\v!...) can be changed, only
>>> 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.
>>
>> My understanding:
>>
>> I translated \setupbodyfont into \configurerfonteprincipale.
>>
>> But I didn't specify any font in the input file.
>>
>> As soon as I specified \configurerfonteprincipale[pagella,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" ?
>
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-06-30 21:02 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 ` Translation of ConTeXt interface Garulfo
2020-06-26 12:16 ` 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 [this message]
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=d5a5c9d4-0c48-0aea-50b9-bed955650935@azules.eu \
--to=garulfo@azules.eu \
--cc=braslau.list@comcast.net \
--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).