From: Gerben Wierda via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Gerben Wierda <gerben.wierda@rna.nl>
Subject: Re: [NTG-context] Linebreaking in Japanese in ConTeXt
Date: Sun, 30 Apr 2023 09:21:22 +0200 [thread overview]
Message-ID: <3E3EDF56-7025-4A19-9354-8FB92E7BC58C@rna.nl> (raw)
In-Reply-To: <CF8FBD57-2166-4A74-B7AB-BAEC9A6F8CB5@rna.nl>
> On 30 Apr 2023, at 09:12, Gerben Wierda via ntg-context <ntg-context@ntg.nl> wrote:
>
> I am currently testing with a Japanese translation of something I originally created in English using the ConTeXt engine (LMTX).
>
> I run into the fact that Japanese has no use for whitespace, so most of the time TeX has no idea where to break. Is there something I can tell ConTeXt to solve this for me or do I have to alk with the translator to put whitespace in the correct places (kind of breaks the automatic linebreaking of TeX, though)?
I forgot to add. I use:
\setuplanguage[ja][patterns={ja}]\mainlanguage[ja]
G
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-04-30 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 7:12 Gerben Wierda via ntg-context
2023-04-30 7:21 ` Gerben Wierda via ntg-context [this message]
2023-04-30 8:04 ` Wolfgang Schuster via ntg-context
2023-04-30 8:48 ` Gerben Wierda via ntg-context
2023-04-30 10:42 ` Wolfgang Schuster via ntg-context
2023-05-01 14:12 ` Henning Hraban Ramm via ntg-context
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=3E3EDF56-7025-4A19-9354-8FB92E7BC58C@rna.nl \
--to=ntg-context@ntg.nl \
--cc=gerben.wierda@rna.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).