From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: Re: Is rendering furigana over horizontal or vertical japanese text doable in ConTeXt?
Date: Mon, 15 Aug 2022 17:39:36 +0200 [thread overview]
Message-ID: <af7c0fd3-9f19-81f2-d19d-e63b5803b2cd@gmail.com> (raw)
In-Reply-To: <eZL3VGzGoIeEaf1Ay6sCPj_qwhmxJaph6R05h7j_7iY8CaTaw1UOjROqoafNlHcJVqDcAl2wHaBQ8xoxtEgAZKQGPeyg5QPoWV31sGVOqGA=@proton.me>
amano.kenji via ntg-context schrieb am 15.08.2022 um 14:00:
> Is there any documentation about \ruby?
You can see all available parameters in setup-en.pdf, the example below
shows a few of them:
%%%% begin example
\setupinterlinespace[line=4ex]
\setuptype[style=\ttx]
\starttext
\start
xxxxxxxxx \ruby{aaa}{bbb} xxxxxxxxx
\stop
\start \setupruby[location=left]
\type{\setupruby[location=left]}\quad xxxxxxxxx \ruby{aaa}{bbb} xxxxxxxxx
\stop
\start \setupruby[location=right]
\type{\setupruby[location=right]}\quad xxxxxxxxx \ruby{aaa}{bbb} xxxxxxxxx
\stop
\start \setupruby[location=right,left={[},right={]}]
\type{\setupruby[left={[},right={]}]}\quad xxxxxxxxx \ruby{aaa}{bbb}
xxxxxxxxx
\stop
\start \setupruby[align=flushleft]
\type{\setupruby[align=flushleft]}\quad xxxxxxxxx \ruby{aaaaaa}{bbb}
xxxxxxxxx
\stop
\start \setupruby[align=flushright]
\type{\setupruby[align=flushright]}\quad xxxxxxxxx \ruby{aaaaaa}{bbb}
xxxxxxxxx
\stop
\start \setupruby[style=\itxx]
\type{\setupruby[style=\itxx]}\quad xxxxxxxxx \ruby{aaa}{bbb} xxxxxxxxx
\stop
\start \setupruby[color=blue]
\type{\setupruby[color=blue]}\quad xxxxxxxxx \ruby{aaa}{bbb} xxxxxxxxx
\stop
\start \setupruby[voffset=-1.2ex]
\type{\setupruby[voffset=-1.2ex]}\quad xxxxxxxxx \ruby{aaa}{bbb} xxxxxxxxx
\stop
\stoptext
%%%% end example
> What about vertical text?
ConTeXt has a mechanism to produce vertical text but there is nothing
yet which can
be used out of the box to produce a complete document with vertical
paragraphs.
Wolfgang
___________________________________________________________________________________
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:[~2022-08-15 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 11:02 amano.kenji via ntg-context
2022-08-15 11:43 ` Taco Hoekwater via ntg-context
2022-08-15 12:00 ` amano.kenji via ntg-context
2022-08-15 15:39 ` Wolfgang Schuster via ntg-context [this message]
2022-08-16 11:33 ` amano.kenji via ntg-context
2022-08-16 15:05 ` Wolfgang Schuster via ntg-context
2022-08-21 8:24 ` 黄复雄 via ntg-context
2022-08-21 10:00 ` Hans Hagen via ntg-context
2022-08-21 10:10 ` Wolfgang Schuster via ntg-context
2022-08-21 16:19 ` Hans Hagen via ntg-context
2022-08-22 5:21 ` 黄复雄 via ntg-context
2022-08-22 7:16 ` Hans Hagen via ntg-context
2022-09-03 10:44 ` 黄复雄 via ntg-context
2022-08-22 2:09 ` 黄复雄 via ntg-context
2022-08-22 4:52 ` 黄复雄 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=af7c0fd3-9f19-81f2-d19d-e63b5803b2cd@gmail.com \
--to=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@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).