cannonballrag at gmail.com
2014-Mar-04 18:13 UTC
Markdown-Discuss Digest, Vol 132, Issue 1
Thanks for the explaination, Fletcher. cannonballrag at gmail.com 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 markdown-discuss at six.pairlist.net 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 markdown-discuss-request at six.pairlist.net You can reach the person managing the list at markdown-discuss-owner at six.pairlist.net 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 (cannonballrag at gmail.com) 2. Re: Hi, question about utf-8 saved source (Fletcher T. Penney) ---------------------------------------------------------------------- Message: 1 Date: Mon, 3 Mar 2014 22:56:30 +0800 From: "cannonballrag at gmail.com" <cannonballrag at gmail.com> Subject: Hi, question about utf-8 saved source To: Markdown-Discuss <Markdown-Discuss at six.pairlist.net> Message-ID: <201403032256281963033 at gmail.com> 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! cannonballrag at gmail.com -------------- 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" <fletcher at fletcherpenney.net> Subject: Re: Hi, question about utf-8 saved source To: "Discussion related to Markdown." <markdown-discuss at six.pairlist.net> Message-ID: <53149953.6010906 at fletcherpenney.net> 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, cannonballrag at gmail.com 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! > ------------------------------------------------------------------------ > cannonballrag at gmail.com > > > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss at six.pairlist.net > http://six.pairlist.net/mailman/listinfo/markdown-discuss >-- Fletcher T. Penney fletcher at fletcherpenney.net ------------------------------ _______________________________________________ Markdown-Discuss mailing list Markdown-Discuss at six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss End of Markdown-Discuss Digest, Vol 132, Issue 1 ************************************************ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20140305/dbbcd0d5/attachment.html>