ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jean-Pierre Delange <adeimantos@free.fr>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Japanese
Date: Sun, 10 Mar 2024 20:26:45 +0100	[thread overview]
Message-ID: <d444d4b4-925f-425f-8bd1-d4f3544517e7@free.fr> (raw)
In-Reply-To: <AC5BC6D1-A561-4292-BAC4-EFC7B0997E0A@getmailspring.com>


[-- Attachment #1.1: Type: text/plain, Size: 5230 bytes --]

Emanuel,

Your sample seems to work fine on CTX MKIV 2024.01.24 version , as far 
as I see the final PDF output. And ConTeXt doesn't complain, even in the 
log !

Best//JP

Le 10/03/2024 à 17:43, Emanuel Han via ntg-context a écrit :
> Hi all,
>
> I added 
> https://wiki.contextgarden.net/Chinese_Japanese_and_Korean#Meeting_the_JIS_X_4051_Requirements_for_Japanese_Text_Layout
> with attached working example code and to-do list.
>
> Thanks for any contributions!
>
> The working example code is still a work in progress. Its text layout 
> output meets already some of the requirements (see comments in the 
> code). Among the ones to still be implemented are:
>
>  *
>     solid setting (no extra spacing between characters)
>     https://www.w3.org/TR/jlreq/#fig1_8 if no requirement for
>     line-adjustment https://www.w3.org/TR/jlreq/#term.line-adjustment
>  *
>     aligning of the lines to the Kihon-hanmen (optimizing the code
>     below in this regard)
>  *
>     positioning and realm of headings
>     https://www.w3.org/TR/jlreq/#fig3_1_9
>     https://www.w3.org/TR/jlreq/#fig3_1_15 et al, and
>     https://www.w3.org/TR/jlreq/#fig3_1_4
>  *
>     positioning of yokugo-ruby https://www.w3.org/TR/jlreq/#fig2_3_24
>  *
>     inline cutting note (warichu) https://www.w3.org/TR/jlreq/#fig2_4_1
>  *
>     emphasis with sesame dot or bullet
>  *
>     itemization https://www.w3.org/TR/jlreq/#fig2_5_6
>  *
>     indenting of quotation paragraphs
>     https://www.w3.org/TR/jlreq/#fig2_5_7
>  *
>     tab setting https://www.w3.org/TR/jlreq/#fig2_6_1
>  *
>     furiwake https://www.w3.org/TR/jlreq/#fig2_7_2
>  *
>     jidori https://www.w3.org/TR/jlreq/#fig2_7_4
>  *
>     math https://www.w3.org/TR/jlreq/#fig2_7_6 and
>     https://www.w3.org/TR/jlreq/#fig2_7_62
>  *
>     tategaki (writing vertically)
>
> Best regards
>
> Emanuel
> On März 2 2024, at 7:00 pm, Wolfgang Schuster 
> <wolfgang.schuster.lists@gmail.com> wrote:
>
>     Emanuel Han schrieb am 01.03.2024 um 16:23:
>
>
>         Dear Wolfgang,
>
>         thank you for your valuable remarks. I integrated them, see
>         corrected attached example.
>
>         Yes, correct layout examples exist. They're all showing
>         vertical writing, but the rules and principles are exactly the
>         same for horizontal writing.
>
>          *
>             position of the headers and footers:
>             https://www.w3.org/TR/jlreq/#fig1_30
>
>
>     See my attached gongitsune.tex example how you can squeeze text in
>     a very narrow header/footer.
>
>          *
>             aligning lines to the text box:
>             https://www.w3.org/TR/jlreq/#fig1_3
>
>
>     You can use the lines key for \setuplayout to let ConTeXt
>     calculate the necessary value for the text height.
>
>          *
>             protrusion of ruby: https://www.w3.org/TR/jlreq/#fig_ad1_6
>
>
>     You're getting this for free because ruby text doesn't take up
>     vertical space, in case vertical text is working it would now
>     stick into the margins as expected.
>
>     \starttext
>     \ruledhbox{a \ruby{x}{y} b}
>     \stoptext
>
>
>          *
>
>
>
>         In my previous mail, I wrote wrong amounts of lines. They
>         should be 46 lines on one page, while the actual example
>         doesn't show the 46th line.
>
>         It would be important to identify the reason why only 24
>         characters are used to create a line when 25 could be used.
>         Then we can develop a method to turn that mechanism off or
>         circumvent it.
>         Quotation from https://www.w3.org/TR/jlreq:
>         /In principle, when composing a line with //ideographic
>         (cl-19) <https://www.w3.org/TR/jlreq/#cl-19>//, //hiragana
>         (cl-15) <https://www.w3.org/TR/jlreq/#cl-15>// and //katakana
>         (cl-16) <https://www.w3.org/TR/jlreq/#cl-16>// characters, no
>         extra spacing appears between their //character frame
>         <https://www.w3.org/TR/jlreq/#term.character-frame>//. This is
>         called solid setting (see //Figure 5
>         <https://www.w3.org/TR/jlreq/#fig1_8>//)./
>
>
>     1. ConTeXt has a mechanism to typeset Japanese texts.
>
>     2. There are flaws in the output it produces but this nothing
>     which can't be fixed.
>
>     3. To fix the problems someone has to be passionate to fix them
>     and we're willing to help here.
>
>     As you can see in my second example file japanese.tex there is a
>     font feature to create half sized parentheses etc. which isn't
>     supported yet by ConTeXt's mechanism for japanese and in case your
>     willing to improve it this should be taken care of as well.
>
>     Wolfgang
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 12529 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
___________________________________________________________________________________

  reply	other threads:[~2024-03-10 19:29 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 [this message]
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
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=d444d4b4-925f-425f-8bd1-d4f3544517e7@free.fr \
    --to=adeimantos@free.fr \
    --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).