From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from cgl.ntg.nl (Cgl.ntg.nl [5.39.185.202]) by inbox.vuxu.org (Postfix) with ESMTP id 4E0AC24CE8 for ; Wed, 28 Feb 2024 20:56:40 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 96C2C4843E7 for ; Wed, 28 Feb 2024 20:56:13 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Authentication-Results: cgl.ntg.nl (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=labonneheure.ch Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GU6Dmqus_fu3 for ; Wed, 28 Feb 2024 20:56:12 +0100 (CET) Received: from cgl.ntg.nl (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 87309484633 for ; Wed, 28 Feb 2024 20:52:48 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id C0DCF484270 for ; Wed, 28 Feb 2024 20:51:56 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjCtnqSsdEhO for ; Wed, 28 Feb 2024 20:51:55 +0100 (CET) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=45.13.66.34; helo=outbound00.knthost.com; envelope-from=emanuel@labonneheure.ch; receiver= Received: from outbound00.knthost.com (outbound00.knthost.com [45.13.66.34]) (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 cgl.ntg.nl (Postfix) with ESMTPS id 757F248426B for ; Wed, 28 Feb 2024 20:51:54 +0100 (CET) Date: Wed, 28 Feb 2024 20:51:46 +0100 DKIM-Filter: OpenDKIM Filter v2.10.3 outbound00.knthost.com E4B3785341 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=labonneheure.ch; s=default; t=1709149910; bh=32mu9VnfCk++/yM5omITYyuwDTe+mV12r9h0KO8N+jc=; h=Date:From:To:In-Reply-To:References:Subject; b=DNgr3tUz0USBaVbxa8ncK6+CnXfm2TdEJXcDKlIDyfzI+meL8pAa9wPvw8Wk8GhZM wm5aA4HjSdAOLbmnOJZoTxxV9XNUFF/dXnv013pWOuuT7tSZzuJriZ6XXMaab4Op4A XEvoTngOqayedBVDKY48t92zM3NuZ/Ccdj6Ibke0kJNrL1UV3phvEce6BR1T6dL9U5 X4eTuQ1zKtnRZ0x2iUzFIbSfs98YhX5zr2dQ14zuOKxorEiPAyo+n9Z78fspn5VvEz IjQzPmM8z3ziEEi1eIPm/0nRth7U8gOxRufsfdnJ6YCTQ34yyFNP+YGiiH7r5JC047 PqS1+sFRKlP8w== To: mailing list for ConTeXt users Message-ID: In-Reply-To: <9bc7fee6-3275-4e7f-8343-c1477ecc14b7@free.fr> References: <9bc7fee6-3275-4e7f-8343-c1477ecc14b7@free.fr> X-Mailer: Mailspring MIME-Version: 1.0 Message-ID-Hash: G3D24YNVOTVLKFUYA24ZZ6XKGGKXF5PJ X-Message-ID-Hash: G3D24YNVOTVLKFUYA24ZZ6XKGGKXF5PJ X-MailFrom: emanuel@labonneheure.ch X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list Reply-To: mailing list for ConTeXt users Subject: [NTG-context] Re: Japanese List-Id: mailing list for ConTeXt users Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Emanuel Han via ntg-context Cc: Emanuel Han Content-Type: multipart/mixed; boundary="===============7646757657524886203==" --===============7646757657524886203== Content-Type: multipart/alternative; boundary="65df8ed2_6b8b4567_15567" --65df8ed2_6b8b4567_15567 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thank you all for your suggestions and contributions to the wiki. I don't intend to nag, but when looking at what ConTeXt is producing, I n= eed to state that the result is still far away from a properly typeset Ja= panese text. So the nihongo script which comes with ConTeXt handles line breaks / line= wrapping. But the line break rules defined in it need a rework, because = they don't follow the standards. The standards are documented here: https= ://www.w3.org/TR/jlreq/=23possibilities=5Ffor=5Flinebreaking=5Fbetween=5F= characters , and all affected characters are listed here: https://www.w3.= org/TR/jlreq/tables/table=5Fen3.pdf We have different rules, depending what kind of character is surpassing t= he text width (or is in its last position). Rule 1: Before closing brackets, closing quotation marks, iteration marks, the Pr= olonged sound mark and small Kana, line breaking is prohibited. =E2=80=99=E2=80=9D=EF=BC=89=E3=80=95=EF=BC=BD=EF=BD=9D=E3=80=89=E3=80=8B=E3= =80=8D=E3=80=8F=E3=80=91=E3=83=BD=E3=83=BE=E3=82=9D=E3=82=9E=E3=80=85=E3=83= =BC=E3=81=81=E3=81=83=E3=81=85=E3=81=87=E3=81=89=E3=82=A1=E3=82=A3=E3=82=A5= =E3=82=A7=E3=82=A9=E3=81=A3=E3=82=83=E3=82=85=E3=82=87=E3=83=83=E3=83=A3=E3= =83=A5=E3=83=A7 etc. The actual programmed behaviour by the nihongo script is that, if in the = position which exceeds the line width, these characters jump to the next = line and take the previous character with them. If they're in the last po= sition of the line, they stay where they are. This behaviour is correct. Rule 2: After opening Brackets and opening quotation marks, line breaking is proh= ibited (but not before). =E2=80=98=E2=80=9C=EF=BC=88=E3=80=94=EF=BC=BB=EF=BD=9B=E3=80=88=E3=80=8A=E3= =80=8C=E3=80=8E=E3=80=90 The actual programmed behaviour by the nihongo script is that these chara= cters jump to the next line and take the previous character with them. Th= is behaviour is wrong. They should jump to the next line without taking t= he previous character with them, just like any regular character. The dif= ference to a regular character is that they jump already when still withi= n the line length, and they're in the last position of the line. The corr= ect behaviour can be seen in LibreOffice Writer in action. Rule 3: Comma (t=C5=8Dten), full width comma, full stop =E3=80=81=EF=BC=8C=E3=80=82 The actual programmed behaviour by the nihongo script is that, if in the = position which exceeds the line width, these characters jump to the next = line and take the previous character with them. This behaviour is wrong. They have to be put back to the end of the previous line, but beyond the = specified line length. (JIS Z 8125) (Search for =22Line adjustment by han= ging punctuation=22 under https://www.w3.org/TR/jlreq/ ) If they're in the last position of the line, they stay where they are. Th= e correct behaviour can be seen in LibreOffice Writer in action. Rules 4, 5, ...: Combinations of inseparable characters... (see https://www.w3.org/TR/jlre= q/=23possibilities=5Ffor=5Flinebreaking=5Fbetween=5Fcharacter ) and event= ually more, which I didn't test. It might be useful to define three scripts nihongo=5Floose, nihongo=5Fstr= ict and nihongo=5Fvery=5Fstrict which each implement one of the 3 cases d= escribed here: https://www.w3.org/TR/jlreq/=23addendum=5Fa According the line gap (Otared uses =5Csetupwhitespace=5Bbig=5D, which is= exceeding common line gaps), I'd like to quote from https://www.w3.org/T= R/jlreq/ : It is common that the line gap for the kihon-hanmen is set to a value bet= ween half-em spacing and the one em spacing of the character frame used f= or the kihon-hanmen. Half-em spacing can be chosen in cases where the lin= e length is short, but one em spacing or close to it is more appropriate = when the line length is longer than 35 characters. I like the standard line gap which is provided by ConTeXt, which is equiv= alent to =5Csetupwhitespace=5B0pt=5D. Even when using ruby, it works well= . I found the best voffset for ruby to be -1.7ex. The line adjustment provided by ConTeXt by default is not meeting the nee= ds for Japanese (and Chinese) text, which follow a grid pattern. Especial= ly the last line of a paragraph is squeezed, which is =22hurting the eye=22= . When characters need to jump to the next line due to previously discussed= line breaking rules, ConTeXt seems to apply =22Line adjustment by inter-= character spacing expansion=22, which is a valid method according to http= s://www.w3.org/TR/jlreq/=23line=5Fadjustment , although =22Line adjustmen= t by inter-character spacing reduction=22 is preferred. The last point which ConTeXt is missing, when talking about Japanese type= setting, is vertical writing. I know, this is a lot of work. Hopefully we can achieve with joint effort= s to make ConTeXt Japanese ready. If I happen to have made false statements, please accept my apology. I tr= ied to be of help as far as I could. I grew up in Japan and know more or = less how typeset text should look like. Emanuel On =46eb. 28 2024, at 7:44 pm, Jean-Pierre Delange = wrote: > Hi Hraban =21 > > I also used to write this, if the main language is European : > =5Cdefinefallbackfamily =5Bmainface=5D =5Brm=5D =5Bipamincho=5D > =5Brange=3Dcjkunifiedideographs=5D > > Hope this is useful anymore, > JP > Le 28/02/2024 =C3=A0 18:34, Henning Hraban Ramm a =C3=A9crit : > > Am 28.02.24 um 08:34 schrieb Otared Kavian: > >> Dear Dalyoung, > >> > >> Thank you very much for your insight. I downloaded the Noto Serif JP= > >> fonts and set up a fontfamily as you indicated, by adding > >> =5Csetscript=5Bnihongo=5D > >> which solves a problem I had with line breakings. And everything > >> works smoothly=21 > >> > >> So, for the mail archive, here is what I have and what works fine: > >> > >> %%% Noto =46onts > >> > >> =5Cdefinefontfamily=5BJapanese=46ont=5D=5Brm=5D=5BNoto Serif JP=5D > >> =5B it=3D=7Bstyle:regular,features:=7B*,slanted=7D=7D, > >> sl=3D=7Bstyle:regular,features:=7B*,slanted=7D=7D, > >> bi=3D=7Bstyle:bold,features:=7B*,slanted=7D=7D,force=3Dyes=5D > >> > >> =5Cdefinefontfamily=5BJapanese=46ont=5D=5Bss=5D=5BNoto Serif JP=5D > >> =5B it=3D=7Bstyle:regular,features:=7B*,slanted=7D=7D, > >> sl=3D=7Bstyle:regular,features:=7B*,slanted=7D=7D, > >> bi=3D=7Bstyle:bold,features:=7B*,slanted=7D=7D,force=3Dyes=5D > >> > >> =5Cdefinefontfamily=5BJapanese=46ont=5D=5Btt=5D=5BNoto Serif JP=5D > >> =5B it=3D=7Bstyle:regular,features:=7B*,slanted=7D=7D, > >> sl=3D=7Bstyle:regular,features:=7B*,slanted=7D=7D, > >> bi=3D=7Bstyle:bold,features:=7B*,slanted=7D=7D,force=3Dyes=5D > >> > >> =5Cdefinefontfamily=5BJapanese=46ont=5D=5Bmath=5D=5BTex Gyre Termes = Math=5D > >> %=5Cdefinefontfamily=5BJapanese=46ont=5D=5Bmath=5D=5BTex Gyre Pagell= a Math=5D > >> %=5Cdefinefontfamily=5BJapanese=46ont=5D=5Bmath=5D=5BTex Gyre Avento= r=5D > >> > >> %%%% > >> > >> =5Csetupbodyfont=5BJapanese=46ont,12pt=5D > >> =5Csetupruby=5Blocation=3Dtop,voffset=3D-2ex=5D > >> =5Csetupwhitespace=5Bbig=5D > >> =5Csetscript=5Bnihongo=5D > >> > >> =5Cstarttext > >> =5Cruby=7B=E6=97=A9=7D=7B=E3=81=AF=E3=82=84=7D=E3=81=8F=E3=80=82 > >> =E3=81=84=E3=81=8D=E3=81=BE=E3=81=97=E3=82=87=E3=81=86=E3=80=82 > >> =5Cstoptext > >> > >> Best regards: Otared > > > > Thanks all contributors, I added this to > > https://wiki.contextgarden.net/Chinese=5FJapanese=5Fand=5FKorean > > > > I guess you also should set =5Cmainlanguage=5Bja=5D, I added it, also= > > =5Cmainlanguage=5Bkr=5D for Korean. > > > > I don=E2=80=99t know if the setups for Chinese and Korean are still v= alid, I > > just removed =5Csetencoding. > > > > Hraban > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > > > > If your question is of interest to others as well, please add an entr= y > > to the Wiki=21 > > > > maillist : ntg-context=40ntg.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 > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F > If your question is of interest to others as well, please add an entry = to the Wiki=21 > > maillist : ntg-context=40ntg.nl / https://mailman.ntg.nl/mailman3/lists= /ntg-context.ntg.nl > webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirro= r) > archive : https://github.com/contextgarden/context > wiki : https://wiki.contextgarden.net > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F > --65df8ed2_6b8b4567_15567 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Thank you all for your suggestions and contributions to the wiki.
I don't intend to nag, but when looking at what ConTeXt is p= roducing, I need to state that the result is still far away from a proper= ly typeset Japanese text.

So the nihongo script which come= s with ConTeXt handles line breaks / line wrapping. But = the line break rules defined in it need a rework, because they don't foll= ow the standards. The standards are documented here: https://www.w3.org/T= R/jlreq/=23possibilities=5Ffor=5Flinebreaking=5Fbetween=5Fcharacters , an= d all affected characters are listed here: https://www.w3.org/TR/jlreq/ta= bles/table=5Fen3.pdf

We have different rules, depending wha= t kind of character is surpassing the text width (or is in its last posit= ion).

Rule 1:

Before closing brackets, clos= ing quotation marks, iteration marks, the Prolonged sound mark and small = Kana, line breaking is prohibited.

=E2=80=99=E2=80=9D=EF=BC= =89=E3=80=95=EF=BC=BD=EF=BD=9D=E3=80=89=E3=80=8B=E3=80=8D=E3=80=8F=E3=80=91= =E3=83=BD=E3=83=BE=E3=82=9D=E3=82=9E=E3=80=85=E3=83=BC=E3=81=81=E3=81=83=E3= =81=85=E3=81=87=E3=81=89=E3=82=A1=E3=82=A3=E3=82=A5=E3=82=A7=E3=82=A9=E3=81= =A3=E3=82=83=E3=82=85=E3=82=87=E3=83=83=E3=83=A3=E3=83=A5=E3=83=A7 etc. <= /div>
The actual programmed behaviour by the nihongo script is th= at, if in the position which exceeds the line width,  these characte= rs jump to the next line and take the previous character with them. If th= ey're in the last position of the line, they stay where they are. This be= haviour is correct.

Rule 2:

After opening B= rackets and opening quotation marks, line breaking is prohibited (but not= before).

=E2=80=98=E2=80=9C=EF=BC=88=E3=80=94=EF=BC=BB=EF=BD= =9B=E3=80=88=E3=80=8A=E3=80=8C=E3=80=8E=E3=80=90

The actua= l programmed behaviour by the nihongo script is that these characters jum= p to the next line and take the previous character with them. This behavi= our is wrong. They should jump to the next line without taking the previo= us character with them, just like any regular character. The difference t= o a regular character is that they jump already when still within the lin= e length, and they're in the last position of the line. The correct behav= iour can be seen in LibreOffice Writer in action.

Rule 3: =

Comma (t=C5=8Dten), full width comma, full stop

<= div>=E3=80=81=EF=BC=8C=E3=80=82

The actual programmed behav= iour by the nihongo script is that, if in the position which exceeds the = line width, these characters jump to the next line and take the previous = character with them. This behaviour is wrong. 
They have= to be put back to the end of the previous line, but beyond the specified= line length. (JIS Z 8125) (Search for =22Line adjustment by hanging punc= tuation=22 under https://www.w3.org/TR/jlreq/ )
If they're in t= he last position of the line, they stay where they are. The correct behav= iour can be seen in LibreOffice Writer in action.

Rules 4,= 5, ...:

Combin= ations of inseparable characters... (see https://www.w3.org/TR/jlreq/=23p= ossibilities=5Ffor=5Flinebreaking=5Fbetween=5Fcharacter ) and eventually = more, which I didn't test.

It might be useful to define thr= ee scripts nihongo=5Floose, nihongo=5Fstrict and nihongo=5Fvery=5Fstrict = which each implement one of the 3 cases described here: https://www.w3.or= g/TR/jlreq/=23addendum=5Fa

According the line gap (Otared uses =5Csetupwhitespace=5Bbig=5D, which is exceeding= common line gaps), I'd like to quote from https://www.w3.org/TR/jlreq/ :=

It is common that the line gap for the kihon-hanmen is= set to a value between half-em spacing and the one em spacing of the cha= racter frame used for the kihon-hanmen. Half-em spacing can be chosen in = cases where the line length is short, but one em spacing or close to it i= s more appropriate when the line length is longer than 35 characters.

I like the standard line gap which is provided by ConTeXt= , which is equivalent to =5Csetupwhitespace=5B0pt=5D. Even when = using ruby, it works well. I found the best voffset for ruby to be -1.7ex= .

The line adjustment provided by Con= TeXt by default is not meeting the needs for Japanese  (and Chinese)= text, which follow a grid pattern. Especially the last line of a paragra= ph is squeezed, which is =22hurting the eye=22.

When chara= cters need to jump to the next line due to previously discussed line brea= king rules, ConTeXt seems to apply =22Line adjustment by inter-character = spacing expansion=22, which is a valid method according to https://www.w3= .org/TR/jlreq/=23line=5Fadjustment , although =22Line adjustment by inter= -character spacing reduction=22 is preferred.

The last poin= t which ConTeXt is missing, when talking about Japanese typesetting, is v= ertical writing.

I know, this is a lot of work. Hopefully = we can achieve with joint efforts to make ConTeXt Japanese ready.
<= br>
If I happen to have made false statements, please accept my apolo= gy. I tried to be of help as far as I could. I grew up in Japan and know = more or less how typeset text should look like.

Emanuel
On =46eb. 28 2024, = at 7:44 pm, Jean-Pierre Delange <adeimantos=40free.fr> wrote:
=
Hi Hraban =21

I also used to write th= is, if the main language is European :

=5Cdefinefallbackfam= ily =5Bmainface=5D =5Brm=5D =5Bipamincho=5D
=5Brange=3Dcjkunifi= edideographs=5D

Hope this is useful anymore,

= JP

Le 28/02/2024 =C3=A0 18:34, Henning Hraban Ramm a =C3=A9= crit :
> Am 28.02.24 um 08:34 schrieb Otared Kavian:
>> Dear Dalyoung,
>>
>> Tha= nk you very much for your insight. I downloaded the Noto Serif JP
>> fonts and set up a fontfamily as you indicated, by adding
>> =5Csetscript=5Bnihongo=5D
>> which solves= a problem I had with line breakings. And everything
>> w= orks smoothly=21
>>
>> So, for the mail a= rchive, here is what I have and what works fine:
>>
=
>> %%% Noto =46onts
>>
>> =5Cd= efinefontfamily=5BJapanese=46ont=5D=5Brm=5D=5BNoto Serif JP=5D
= >>    =5B   it=3D=7Bstyle:regular,features:=7B*,slan= ted=7D=7D,
>>        sl=3D=7Bstyle:re= gular,features:=7B*,slanted=7D=7D,
>>     =   bi=3D=7Bstyle:bold,features:=7B*,slanted=7D=7D,force=3Dyes=5D
>>
>> =5Cdefinefontfamily=5BJapanese=46ont=5D= =5Bss=5D=5BNoto Serif JP=5D
>>    =5B   it= =3D=7Bstyle:regular,features:=7B*,slanted=7D=7D,
>>  = ;      sl=3D=7Bstyle:regular,features:=7B*,slanted=7D=7D,<= /div>
>>        bi=3D=7Bstyle:bold,features= :=7B*,slanted=7D=7D,force=3Dyes=5D
>>
>> = =5Cdefinefontfamily=5BJapanese=46ont=5D=5Btt=5D=5BNoto Serif JP=5D
<= div>>>    =5B   it=3D=7Bstyle:regular,features:=7B*,= slanted=7D=7D,
>>        sl=3D=7Bstyl= e:regular,features:=7B*,slanted=7D=7D,
>>    &n= bsp;   bi=3D=7Bstyle:bold,features:=7B*,slanted=7D=7D,force=3Dyes=5D=
>>
>> =5Cdefinefontfamily=5BJapanese=46o= nt=5D=5Bmath=5D=5BTex Gyre Termes Math=5D
>> %=5Cdefinefo= ntfamily=5BJapanese=46ont=5D=5Bmath=5D=5BTex Gyre Pagella Math=5D
>> %=5Cdefinefontfamily=5BJapanese=46ont=5D=5Bmath=5D=5BTex Gyre= Aventor=5D
>>
>> %%%%
>>=
>> =5Csetupbodyfont=5BJapanese=46ont,12pt=5D
&= gt;> =5Csetupruby=5Blocation=3Dtop,voffset=3D-2ex=5D
>>= ; =5Csetupwhitespace=5Bbig=5D
>> =5Csetscript=5Bnihongo=5D=
>>
>> =5Cstarttext
>> =5C= ruby=7B=E6=97=A9=7D=7B=E3=81=AF=E3=82=84=7D=E3=81=8F=E3=80=82
&= gt;> =E3=81=84=E3=81=8D=E3=81=BE=E3=81=97=E3=82=87=E3=81=86=E3=80=82
>> =5Cstoptext
>>
>> Best = regards: Otared
>
> Thanks all contributors, I = added this to
> https://wiki.contextgarden.net/Chinese=5FJap= anese=5Fand=5FKorean
>
> I guess you also shoul= d set =5Cmainlanguage=5Bja=5D, I added it, also
> =5Cmainlan= guage=5Bkr=5D for Korean.
>
> I don=E2=80=99t k= now if the setups for Chinese and Korean are still valid, I
>= ; just removed =5Csetencoding.
>
> Hraban
=
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
>
> If you= r question is of interest to others as well, please add an entry
> to the Wiki=21
>
> maillist : ntg-contex= t=40ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-con= text.ntg.nl
> webpage  : https://www.pragma-ade.nl / ht= tps://context.aanhet.net
> (mirror)
> archive&n= bsp; : https://github.com/contextgarden/context
> wiki =     : https://wiki.contextgarden.net
> =5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F
>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
If your question is of interest to others as well, please add an e= ntry to the Wiki=21

maillist : ntg-context=40ntg.nl / https= ://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : h= ttps://www.pragma-ade.nl / https://context.aanhet.net (mirror)
= archive : https://github.com/contextgarden/context
wiki : https= ://wiki.contextgarden.net
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
<= /blockquote> --65df8ed2_6b8b4567_15567-- --===============7646757657524886203== 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://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 ___________________________________________________________________________________ --===============7646757657524886203==--