From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Straight Quotes / Curly Quotes
Date: Fri, 18 Jun 2021 00:35:27 +0200 [thread overview]
Message-ID: <67611183-ad56-b670-9b21-06a543a64b9b@xs4all.nl> (raw)
In-Reply-To: <D2691829-4D0E-4EDB-A09A-AD617F86E436@fiee.net>
On 6/18/2021 12:10 AM, Henning Hraban Ramm wrote:
> I usually convert all kinds of quotation marks into \quotation{} / \quote{} using the regex search of my editor; a regex replacement is also part of my docx-to-ConTeXt converter script. (I see no need to avoid regexes, but YMMV.)
>
> The biggest problem I face are mixed and wrong quotation marks, e.g. English marks in a German text, a mixture of curly/straight marks, traditional LaTeX q. marks and similar mistakes. Some programs have a default of English single quotes with German double quotes :(
>
> In what kind of workflows does your program make sense?
> (Please don’t be offended, my view is limited.)
lua is normally fast enough to handle it wirh a few expresions or lpeg
but in the end it depends on hwo far one will go
for instance, if it is for converting gutenberg files that extensive
conversion can help ... with intermediate test runs (for instance
coloring quitations quickly shows a runaway that then can be fixed in
the input
For instance:
"Not all open quotes are closed...
kind of tricky because there one needs to know the source so there is no
real universal solution (one could layer it)
in the past we had projects where we did the rendering and used tex but
the rendering was trivial ... they came to us because we were able to
turn crap into useful (it's unbelievable what can come from databases or
generated from web applications, lack of symmetry, multiple escaping,
bad encodings, inconsistencies) ... unfortunately the money is often
already spent in getting to the stage where the crap is produced
but anyway after year sone kind of knows that there is always a solution
(also because tex and related tools are so flexible and can help with
diagnosing)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-06-17 22:35 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 [this message]
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
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=67611183-ad56-b670-9b21-06a543a64b9b@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).