From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE, T_SCC_BODY_TEXT_LINE,URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6262 invoked from network); 30 Apr 2023 07:18:05 -0000 Received: from zapf.ntg.nl (5.39.185.232) by inbox.vuxu.org with ESMTPUTF8; 30 Apr 2023 07:18:05 -0000 Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 0553413C3; Sun, 30 Apr 2023 09:17:41 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anWHbEcXJ1X8; Sun, 30 Apr 2023 09:17:36 +0200 (CEST) Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 887B41C2B85; Sun, 30 Apr 2023 09:17:36 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 9C6A91C2B85 for ; Sun, 30 Apr 2023 09:17:34 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjrCH50xx9Xc for ; Sun, 30 Apr 2023 09:17:33 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=213.125.118.53; helo=mail.rna.nl; envelope-from=gerben.wierda@rna.nl; receiver= X-Greylist: delayed 291 seconds by postgrey-1.36 at zapf.ntg.nl; Sun, 30 Apr 2023 09:17:32 CEST Received: from mail.rna.nl (mail.rna.nl [213.125.118.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 03F9513C3 for ; Sun, 30 Apr 2023 09:17:32 +0200 (CEST) Received: from smtpclient.apple (hermione.rna.nl [192.168.2.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by albus.rna.nl (Postfix) with ESMTPSA id 788B417603D40 for ; Sun, 30 Apr 2023 09:12:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rna.nl; s=dkim_rsa2048; t=1682838759; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=W64PThFDf6iKVh3cfxCXt4Nnd3G0XUkklC6woeTUVko=; b=pT4c82LWROL8oBx7bAg0WvZ6kfV668YYSRM9kmuKSCgZy+sKCBEy6bS0bG45zs8fnEbol8 /wsmEw9UYID962dt3NWFLCdphB7NuFFS2lrvIbz2+ZSwmp6i+hvAd2i2ihO5i7GTILbZFr g/+6dgErcgRkdLsj4UH0u5vCtAZg7FrDkZYnQ3GEPINSj9vVfU3LZm9GuYPuPuRMUlzZ71 sdDfKZIOPbSJvx1944tMPEGafnLq/y1y8TegSxTAXKXrjVWAysq4ybA5gHxbDqyibarAU3 ACQqpAxmgeHuOs70gQJeiQ8feurx461IcX3VkkO1hMGZWQ4rcju3IEVLn2H22g== Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Message-Id: Date: Sun, 30 Apr 2023 09:12:37 +0200 To: mailing list for ConTeXt users X-Mailer: Apple Mail (2.3696.120.41.1.3) Subject: [NTG-context] Linebreaking in Japanese in ConTeXt X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.38 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Gerben Wierda via ntg-context Reply-To: mailing list for ConTeXt users Cc: Gerben Wierda Content-Type: multipart/mixed; boundary="===============6327572561702482507==" Errors-To: ntg-context-bounces@ntg.nl Sender: "ntg-context" --===============6327572561702482507== Content-Type: multipart/alternative; boundary="Apple-Mail=_DC144CE9-6AD9-49E5-9368-B7E43DEECCDC" --Apple-Mail=_DC144CE9-6AD9-49E5-9368-B7E43DEECCDC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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)? Gerben Wierda (LinkedIn , = Mastodon ) R&A IT Strategy (main site) Book: Chess and the Art of Enterprise=C2=A0Architecture = Book: Mastering ArchiMate --Apple-Mail=_DC144CE9-6AD9-49E5-9368-B7E43DEECCDC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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)?
= --Apple-Mail=_DC144CE9-6AD9-49E5-9368-B7E43DEECCDC-- --===============6327572561702482507== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ 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 ___________________________________________________________________________________ --===============6327572561702482507==--