Thanks for the explaination, Fletcher.
[email protected]
From: markdown-discuss-request
Date: 2014-03-04 01:00
To: markdown-discuss
Subject: Markdown-Discuss Digest, Vol 132, Issue 1
Send Markdown-Discuss mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://six.pairlist.net/mailman/listinfo/markdown-discuss
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Markdown-Discuss digest..."
Today's Topics:
1. Hi, question about utf-8 saved source ([email protected])
2. Re: Hi, question about utf-8 saved source (Fletcher T. Penney)
----------------------------------------------------------------------
Message: 1
Date: Mon, 3 Mar 2014 22:56:30 +0800
From: "[email protected]" <[email protected]>
Subject: Hi, question about utf-8 saved source
To: Markdown-Discuss <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="gb2312"
Hi, does Markdown.pl have any options to support utf-8 saved source?
currently, i can only solve it by adding a html utf-8 header like below:
<meta http-equiv='Content-Type' content='text/html; charset=utf-8'>
Thanks!
[email protected]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://six.pairlist.net/pipermail/markdown-discuss/attachments/20140303/c6e560a4/attachment-0001.htm>
------------------------------
Message: 2
Date: Mon, 03 Mar 2014 10:01:39 -0500
From: "Fletcher T. Penney" <[email protected]>
Subject: Re: Hi, question about utf-8 saved source
To: "Discussion related to Markdown."
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Markdown.pl proper (the original perl script by John Gruber) doesn't
create complete HTML documents. It creates HTML that is intended to be
inserted inside a "wrapper" that forms a complete HTML document. It
therefore has no concept of character encoding, since that should be
handled by the wrapper (in the `<head>` for example).
Some other Markdown variants (e.g. my MultiMarkdown) can create
"complete" HTML documents, including a `<head>` and the like. By doing
that, they can support UTF-8. For example, in MMD just include some
metadata (such as a title, or author), and the result is a complete HTML
document with UTF-8 support.
Otherwise if you want to stick with Markdown.pl, your solution is
probably the best available.
Fletcher
http://fletcherpenney.net/multimarkdown/
On 3/3/14, 9:56 AM, [email protected] wrote:
> Hi, does Markdown.pl have any options to support utf-8 saved source?
> currently, i can only solve it by adding a html utf-8 header like below:
> <meta http-equiv='Content-Type' content='text/html; charset=utf-8'>
> Thanks!
> ------------------------------------------------------------------------
> [email protected]
>
>
> _______________________________________________
> Markdown-Discuss mailing list
> [email protected]
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>
--
Fletcher T. Penney
[email protected]
------------------------------
_______________________________________________
Markdown-Discuss mailing list
[email protected]
http://six.pairlist.net/mailman/listinfo/markdown-discuss
End of Markdown-Discuss Digest, Vol 132, Issue 1
************************************************
_______________________________________________
Markdown-Discuss mailing list
[email protected]
http://six.pairlist.net/mailman/listinfo/markdown-discuss
