ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Thangalin <thangalin@gmail.com>
Subject: Re: Straight Quotes / Curly Quotes
Date: Fri, 18 Jun 2021 08:09:12 +0200	[thread overview]
Message-ID: <d138b69f-94bb-8577-2e67-d72d8b9d2421@xs4all.nl> (raw)
In-Reply-To: <CAANrE7rK9Cj7-wDUeHdqogJHQB+wCyVLT3L5X0FPk0+kWWZZzg@mail.gmail.com>

On 6/18/2021 4:08 AM, Thangalin wrote:
> Hraban,
> 
>  > In what kind of workflows does your program make sense?
> 
> Have you looked around the web lately?
> 
> KeenWrite (https://github.com/DaveJarvis/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.
what do you mean with 'latex curls quotes' .. can you give an example

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  6:09 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 [this message]
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=d138b69f-94bb-8577-2e67-d72d8b9d2421@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=thangalin@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).