ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Joel via ntg-context <ntg-context@ntg.nl>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Cc: Joel <uaru99@yahoo.com>
Subject: Does writing \emdash versus writing "—" in the source file impact the displayed output?
Date: Wed, 18 May 2022 12:48:14 +0000 (UTC)	[thread overview]
Message-ID: <126306237.2643397.1652878094265@mail.yahoo.com> (raw)
In-Reply-To: <126306237.2643397.1652878094265.ref@mail.yahoo.com>


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

I have been using \endash, \emdash, and \figuredash in place of the various types of dashes in my document, \quotation{} around quotes, etc. so basically the only really punctuation appearing in the tex file are periods, commas, semi-colons, colons, apostrophes, and question-marks. The problem I have is when copying to a tool like Grammarly for grammar checks, these special symbols throw off the grammar-checking tools.

Does ConTeXt render and display these punctuation differently when I write them in the coded form, versus simply writing in the unicode directly?
--Joel

[-- Attachment #1.2: Type: text/html, Size: 952 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:[~2022-05-18 12:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <126306237.2643397.1652878094265.ref@mail.yahoo.com>]

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=126306237.2643397.1652878094265@mail.yahoo.com \
    --to=ntg-context@ntg.nl \
    --cc=uaru99@yahoo.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).