Opened 14 years ago
Last modified 7 years ago
#9343 new enhancement
Because Trac support for multiple repos, each repo with a related encoding.
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | version control | Version: | 0.12dev |
| Severity: | minor | Keywords: | bitesized charset encoding |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
So I recommend for each repos, set an distinct default charset for it.
Attachments (0)
Change History (5)
comment:1 by , 14 years ago
| Component: | general → version control |
|---|---|
| Keywords: | bitesized added |
| Milestone: | → next-major-0.1X |
| Priority: | normal → low |
| Severity: | normal → minor |
| Type: | defect → enhancement |
| Version: | → 0.12dev |
follow-up: 3 comment:2 by , 14 years ago
It's necessary for l10n support, or I'll see the mess code, that's really not good!
comment:3 by , 14 years ago
Replying to luoyonggang@…:
It's necessary for l10n support, or I'll see the mess code, that's really not good!
Sure, but if you want to see something happening sooner, all you need is to fix the issue by yourself (or find someone who will), then contribute the change back to be sure it will stay maintained; in other words, send us a (good) patch.
The keyword bitesized is a hint that it shouldn't be to hard to implement the feature, so it might be a good opportunity to learn about Trac internals and a way to start contributing.
comment:4 by , 13 years ago
| Priority: | low → normal |
|---|
We need the ability to add extra properties to repository resources ("encoding" here).
In the meantime, you can try to specify a list of encodings, each encoding will be tried in turn (see [hg] encoding).
comment:5 by , 7 years ago
| Keywords: | charset encoding added |
|---|
Indeed, but it's rather an enhancement request.