From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Straight Quotes / Curly Quotes
Date: Thu, 17 Jun 2021 19:08:02 -0700 [thread overview]
Message-ID: <CAANrE7rK9Cj7-wDUeHdqogJHQB+wCyVLT3L5X0FPk0+kWWZZzg@mail.gmail.com> (raw)
In-Reply-To: <D2691829-4D0E-4EDB-A09A-AD617F86E436@fiee.net>
[-- Attachment #1.1: Type: text/plain, Size: 1113 bytes --]
Hraban,
> In what kind of workflows does your program make sense?
Have you looked around the web lately?
KeenWrite (https://github.com/DaveJarvis/keenwrite), my plain text editor,
can neither convert nor easily type curly quotes into the application.
Recently, I added ConTeXt integration for exporting to PDF files. ConTeXt
doesn't curl the quotes, which I found a little surprising (because LaTeX
has a quote curling package). Not seeing an obvious solution, I coded my
own library because all the other libraries I found were either not up to
the task or required a massive natural language parser dependency.
My workflow will be: Edit plain text in KeenWrite, export to XHTML, curl
the quotes, run ConTeXt to typeset XHTML.
Another workflow: Edit plain text in KeenWrite, export to XHTML, curl the
quotes, upload to CMS.
The problem is that when typewriters were invented, curly quotes didn't
make it onto the popular layouts. Then, after Unicode, curly closing single
quotes and curly apostrophes were not made unique. HTML entities get it
right, though, with l/rdquo, l/rsquo, and apos. C'est la vie.
[-- Attachment #1.2: Type: text/html, Size: 1515 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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-06-18 2:08 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 [this message]
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
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=CAANrE7rK9Cj7-wDUeHdqogJHQB+wCyVLT3L5X0FPk0+kWWZZzg@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).