<feed xmlns='http://www.w3.org/2005/Atom'>
<title>external_python_mako/test/templates/chs_utf8.html, branch master</title>
<subtitle>Python mako
</subtitle>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/external_python_mako/'/>
<entry>
<title>Switch template encoding to utf-8</title>
<updated>2020-05-29T20:25:11+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2020-05-29T20:25:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/external_python_mako/commit/?id=68b74a1bf581433b59bfb1656b654018607c092d'/>
<id>68b74a1bf581433b59bfb1656b654018607c092d</id>
<content type='text'>
The default template encoding is now utf-8.  Previously, the encoding was
"ascii", which was standard throughout Python 2.   This allows that
"magic encoding comment" for utf-8 templates is no longer required.

Fixes: #267
Change-Id: I411a75ebd6161e2517e06b5180a3571e5f5d923e
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The default template encoding is now utf-8.  Previously, the encoding was
"ascii", which was standard throughout Python 2.   This allows that
"magic encoding comment" for utf-8 templates is no longer required.

Fixes: #267
Change-Id: I411a75ebd6161e2517e06b5180a3571e5f5d923e
</pre>
</div>
</content>
</entry>
<entry>
<title>Use Emacs compatible coding system</title>
<updated>2013-08-28T08:00:39+00:00</updated>
<author>
<name>Martin Geisler</name>
<email>martin@geisler.net</email>
</author>
<published>2013-08-28T08:00:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/external_python_mako/commit/?id=8c079b3b0a06a7e7328d67f74012367878884935'/>
<id>8c079b3b0a06a7e7328d67f74012367878884935</id>
<content type='text'>
Emacs doesn't recognize "utf8" as a valid coding system. The correct
name is "utf-8". This is in line with the UTF-8 FAQ:

  http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8

  The official name and spelling of this encoding is UTF-8, where UTF
  stands for UCS Transformation Format. Please do not write UTF-8 in
  any documentation text in other ways (such as utf8 or UTF_8), unless
  of course you refer to a variable name and not the encoding itself.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Emacs doesn't recognize "utf8" as a valid coding system. The correct
name is "utf-8". This is in line with the UTF-8 FAQ:

  http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8

  The official name and spelling of this encoding is UTF-8, where UTF
  stands for UCS Transformation Format. Please do not write UTF-8 in
  any documentation text in other ways (such as utf8 or UTF_8), unless
  of course you refer to a variable name and not the encoding itself.
</pre>
</div>
</content>
</entry>
<entry>
<title>Use "coding:" instead of "encoding:" to specify file encoding</title>
<updated>2013-08-28T07:58:18+00:00</updated>
<author>
<name>Martin Geisler</name>
<email>martin@geisler.net</email>
</author>
<published>2013-08-28T07:46:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/external_python_mako/commit/?id=66b2d23961b02b86e0ff26b3ffcb6405f7dcedf1'/>
<id>66b2d23961b02b86e0ff26b3ffcb6405f7dcedf1</id>
<content type='text'>
Using "-*- encoding:utf-8 -*-" doesn't really set the file encoding
for Emacs. It will even prompt the user when opening a compiled file:

  The local variables list in foo.mak.py
  contains values that may not be safe (*).

  Do you want to apply it?  You can type
  y  -- to apply the local variables list.
  n  -- to ignore the local variables list.

  !  -- to apply the local variables list, and permanently mark these
        values (*) as safe (in the future, they will be set automatically.)

    * encoding: utf-8

The problem is that Emacs looks for a file variable named "coding" and
it doesn't know about "encoding":

  http://www.gnu.org/software/emacs/manual/html_node/emacs/Specify-Coding.html

This is no doubt why Python recognizes "coding:" by itself:

  http://www.python.org/dev/peps/pep-0263/

This change makes the code generator output "# -*- coding:%s -*-" and
updates the documentation and examples to match this style.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Using "-*- encoding:utf-8 -*-" doesn't really set the file encoding
for Emacs. It will even prompt the user when opening a compiled file:

  The local variables list in foo.mak.py
  contains values that may not be safe (*).

  Do you want to apply it?  You can type
  y  -- to apply the local variables list.
  n  -- to ignore the local variables list.

  !  -- to apply the local variables list, and permanently mark these
        values (*) as safe (in the future, they will be set automatically.)

    * encoding: utf-8

The problem is that Emacs looks for a file variable named "coding" and
it doesn't know about "encoding":

  http://www.gnu.org/software/emacs/manual/html_node/emacs/Specify-Coding.html

This is no doubt why Python recognizes "coding:" by itself:

  http://www.python.org/dev/peps/pep-0263/

This change makes the code generator output "# -*- coding:%s -*-" and
updates the documentation and examples to match this style.
</pre>
</div>
</content>
</entry>
<entry>
<title>begin to modernize testing.  in particular, get rid of test_htdocs as well as ad-hoc</title>
<updated>2010-03-02T22:33:04+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2010-03-02T22:33:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/external_python_mako/commit/?id=16326e69035fd606dd563eaf322033304da8c20c'/>
<id>16326e69035fd606dd563eaf322033304da8c20c</id>
<content type='text'>
HTML file writing, consistently cleanup the modules/cache directories, use
nose skiptests for unsupported features.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
HTML file writing, consistently cleanup the modules/cache directories, use
nose skiptests for unsupported features.
</pre>
</div>
</content>
</entry>
</feed>
