public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Stefan Björk" <stefan.bjork-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: ligatures in html
Date: Tue, 22 Sep 2015 10:12:31 +0000	[thread overview]
Message-ID: <CABsBQU7Qm4W5tnEqXsOz7AW7X=BitNP0PWj+Yo68CiKknnexTA@mail.gmail.com> (raw)
In-Reply-To: <874daeba-ced3-4d7d-b2ad-b0178e5a079b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3607 bytes --]

Sorry for cutting in, but I wonder why using TeX macros in markdown in the
first place? As Jason and David points out, the 'Æ' ligature is available
in UTF-8 (and latin-1 as well, I think, since 'æ' is a characther of its
own in some Nordic countries), and since all modern variants of TeX, namely
XeTeX and LuaTeX, more or less requires UTF-8. By far, the easiest solution
should be to simply use the 'æ' character in markdown -- unless there are
some requirements of ascii-only markdown?

And yes, pandoc converts three dots '...' to an ellipsis '…', but '...' is
not a TeX macro.

tis 22 sep. 2015 kl 11:53 skrev <david.pw.smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:

> I think the more obvious problem is that LaTeX doesn't handle UTF-8 well.
> If UTF-8 is properly supported then you don't need escape characters at
> all, you can just type the æ. These examples would work fine in both html
> and XeTeX/XeLaTeX:
>
> echo "... ærobic" | pandoc -s -f markdown -t html -o test.html
>
> echo "... ærobic" | pandoc -s -f markdown -t latex -o test.tex
>
> You can see for yourself with:
>
> echo "... ærobic" | pandoc -s -f markdown --latex-engine=xelatex -o
> test.pdf
>
> Indeed, for me, Pandoc's default tex template outputs the unicode
> characters correctly, but this could be because my environment is set up to
> use XeLaTeX.
>
> Hope that clarifies a bit?
>
>
>
>
>
> On Monday, 21 September 2015 11:57:37 UTC+1, Chris Wright wrote:
>>
>> I want to publish a document with an \ae ligature to html and to pdf. The
>> latex form "\ae robic" converts to the appropriate form and displays
>> properly in pdf, but the html just drops the ligature.
>>
>>
>> Simple test case:
>>
>>
>> chriswri$ cat > test.txt
>>
>> \ae robic
>>
>> chriswri$ more test.txt
>>
>> \ae robic
>>
>> chriswri$ pandoc -t native test.txt
>>
>> [Para [RawInline (Format "tex") "\\ae ",Str "robic"]]
>>
>> chriswri$ pandoc -t html test.txt
>>
>> <p>robic</p>
>>
>>
>> What's the best way around this - write a filter? finding some docs that
>> will help? (I've found that ... is automatically converted to an ellipsis
>>  - so \dots isn't necessary).
>>
>>
>> with thanks
>>
>>
>> Chris
>>
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/874daeba-ced3-4d7d-b2ad-b0178e5a079b%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/874daeba-ced3-4d7d-b2ad-b0178e5a079b%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CABsBQU7Qm4W5tnEqXsOz7AW7X%3DBitNP0PWj%2BYo68CiKknnexTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 5067 bytes --]

  parent reply	other threads:[~2015-09-22 10:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 10:57 Chris Wright
     [not found] ` <7d633ff1-c25d-436c-a66f-9a8456699db6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-09-21 14:50   ` 'Jason Seeley' via pandoc-discuss
     [not found]     ` <bbaae9b2-c139-415f-9063-86a887358b4c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-09-21 20:54       ` John MACFARLANE
     [not found]         ` <20150921205458.GA92420-4kKid1p5UN4xFjuZnxJpBp3lxR28IOakuDuwTybUTCk@public.gmane.org>
2015-09-22  1:03           ` Chris Wright
2015-09-22  9:52   ` david.pw.smith-Re5JQEeQqe8AvxtiuMwx3w
     [not found]     ` <874daeba-ced3-4d7d-b2ad-b0178e5a079b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-09-22 10:12       ` Stefan Björk [this message]
2015-09-22 10:26       ` Joost Kremers
     [not found]         ` <87twqmycla.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2015-09-23  3:37           ` Chris Wright

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='CABsBQU7Qm4W5tnEqXsOz7AW7X=BitNP0PWj+Yo68CiKknnexTA@mail.gmail.com' \
    --to=stefan.bjork-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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).