From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Otared Kavian <otared@gmail.com>
Subject: [NTG-context] Re: Japanese
Date: Sat, 16 Mar 2024 09:54:47 +0100 [thread overview]
Message-ID: <bfd4e996-9bd3-6566-4648-bd3c205c7ded@gmail.com> (raw)
In-Reply-To: <361B8E66-54C4-43E3-8CC2-F78A904BE096@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]
Otared Kavian schrieb am 14.03.2024 um 14:48:
> Dear Emmanuel,
>
> Thank you for your reply: indeed I understand your approach, which is
> quite efficient. I am not at all good in coding, so I naively thought
> there would be a way for your setup to retrieve the information it
> needs from what the user is doing. Maybe once things are settled, Hans
> and Wolfgang will have a look in the Japanese part of ConTeXt so that
> the user can avoid to enter the setup included in the \directlua part.
There is no need for these calculations because
1. you can create named layouts (e.g. \definelayout[kinohanmen:a4])
for each paper size,
2. you can put the fontsize etc. settings in a setups block and
load the one needed for each paper size and
3. you can put all of them in a module which can be loaded when
writing documents in japanese, the paper size can be passed as argument
to the module.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 1464 bytes --]
[-- Attachment #2: Type: text/plain, Size: 511 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-03-16 8:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 20:08 [NTG-context] Japanese Otared Kavian
2024-02-26 20:16 ` [NTG-context] Japanese Henning Hraban Ramm
2024-02-26 21:49 ` Otared Kavian
2024-02-27 12:55 ` Jeong Dal via ntg-context
2024-02-28 7:34 ` Otared Kavian
2024-02-28 17:34 ` Henning Hraban Ramm
2024-02-28 18:44 ` Jean-Pierre Delange
2024-02-28 19:51 ` Emanuel Han via ntg-context
2024-02-28 20:54 ` Henning Hraban Ramm
2024-02-28 21:18 ` Wolfgang Schuster
2024-02-29 14:18 ` Jeong Dal via ntg-context
2024-03-01 7:04 ` luigi scarso
2024-03-01 12:08 ` Emanuel Han via ntg-context
2024-03-01 13:59 ` Wolfgang Schuster
2024-03-01 15:23 ` Emanuel Han via ntg-context
2024-03-01 16:19 ` Henning Hraban Ramm
2024-03-02 18:00 ` Wolfgang Schuster
2024-03-10 16:43 ` Emanuel Han via ntg-context
2024-03-10 19:26 ` Jean-Pierre Delange
2024-03-11 22:48 ` Wolfgang Schuster
2024-03-13 14:55 ` Otared Kavian
2024-03-14 7:12 ` Emanuel Han via ntg-context
2024-03-14 13:48 ` Otared Kavian
2024-03-16 8:54 ` Wolfgang Schuster [this message]
2024-03-15 8:41 ` luigi scarso
2024-02-26 20:29 ` Hans Hagen
2024-02-26 20:32 ` Emanuel Han via ntg-context
2024-02-26 21:46 ` Otared Kavian
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=bfd4e996-9bd3-6566-4648-bd3c205c7ded@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=otared@gmail.com \
/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).