#7405 closed enhancement (wontfix)
need a charset solution based on directory
Reported by: | lennie | Owned by: | |
---|---|---|---|
Priority: | lowest | Milestone: | |
Component: | version control/browser | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
This is a feature request.
I have a project,but one module's charset is UTF-8,and another modules' charset is GBK。
but in trac.ini,I only can set a default charset setting, if I set charset as UTF-8,then all GBK source code will not display correctly,all non-ascii code are garbages。
If charset can based on directory,then all problem resolved.
such as:
[trac]
default_charset = UTF-8
[trac : foo/bar]
charset = UTF-8
[trac : foo/blahblah]
charset = GBK
Attachments (0)
Change History (4)
follow-up: 2 comment:1 by , 16 years ago
comment:2 by , 16 years ago
Priority: | normal → lowest |
---|
Replying to anonymous:
Well, first of all your suggested implementation wouldn't really make much sense. But aside from that, you should just include the correct encoding in the mimetype. Just set your files to
text/plain;charset=GBK
or whatever.
OK,It's my ignorance,sorry
comment:3 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:4 by , 16 years ago
Note that we'll eventually need such a solution for Mercurial - see #7160.
Well, first of all your suggested implementation wouldn't really make much sense. But aside from that, you should just include the correct encoding in the mimetype. Just set your files to
text/plain;charset=GBK
or whatever.