#2270: TG2b6's update and the project template's encoding
-------------------------+--------------------------------------------------
Reporter: hhsuper | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 2.0rc1
Component: TurboGears | Version: trunk
Severity: major | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by chrisz):
You actually don't need the encoding hints for the quickstarted project
and as long as you only use ascii chars, but they also won't harm in this
case.
But once you start using non-ascii chars you will need the encoding hints,
so they have been added to spare you some typing. The utf-8 encoding has
been chosen since this is what we recommend and most people want to use.
So you can just go ahead, enter your non-ascii chars and save the files.
If you editor doesn't save this as utf-8 you should check the
configuration of your editor, this has nothing to do with TG.
By adding a UTF-8 BOM at the top of the file, we could theoretically give
the editor a broad hint that it should use UTF-8. But this is not yet very
common and would cause more harm than use, since many tools don't expect
it (e.g. I noticed gettext has problems with BOMs, and some other Unix
tools expect the shebang at the exact start of the file) or give warnings
that may confuse users.
--
Ticket URL: <http://trac.turbogears.org/ticket/2270#comment:9>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
