ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Straight Quotes / Curly Quotes
Date: Fri, 18 Jun 2021 09:05:40 -0700	[thread overview]
Message-ID: <CAANrE7p-kz=PmexizWjR5yLv5o07oe-3M+T1WA5NXJQAw6AP_Q@mail.gmail.com> (raw)
In-Reply-To: <DACD622B-D20C-4307-875C-A59936E4C16C@fiee.net>


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

> In HTML you should be able to use <q> – I know that doesn’t work reliably
in browsers (some add straight quotes to my CSS-configured guillemets).

The Converter class maps token replacements:

https://github.com/DaveJarvis/keenquotes/blob/d6c9761f8fe1ae96391f25dc73be52050a148e37/src/main/java/com/whitemagicsoftware/keenquotes/Converter.java#L15

It'd be trivial to use <q> and </q>, instead. For my purposes, HTML
entities work.

> Using \quotation / \quote I avoid typing quotation marks in most cases.

When writing plain text documents, adding TeX code or HTML code to
prescribe how the document should be presented is best avoided, so as to
keep the document decoupled from a particular tool chain. YMMV. A deeper
solution allows users to type the correctly curled quotes directly into the
document.

[-- Attachment #1.2: Type: text/html, Size: 1193 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-06-18 16:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 20:28 Thangalin
2021-06-17 22:10 ` Henning Hraban Ramm
2021-06-17 22:35   ` Hans Hagen
2021-06-18  2:08   ` Thangalin
2021-06-18  6:09     ` Hans Hagen
2021-06-18 15:48       ` Thangalin
2021-06-18 17:12         ` Hans Hagen
2021-06-18 10:00     ` Henning Hraban Ramm
2021-06-18 16:05       ` Thangalin [this message]
2021-06-18 17:03         ` Hans Hagen

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='CAANrE7p-kz=PmexizWjR5yLv5o07oe-3M+T1WA5NXJQAw6AP_Q@mail.gmail.com' \
    --to=thangalin@gmail.com \
    --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).