Opened 16 years ago
Closed 16 years ago
#7976 closed defect (worksforme)
Anchor with accentuated characters don't work
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | wiki system | Version: | none |
Severity: | normal | Keywords: | needinfo |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
This is a fact a very old issue, already present in 0.10. If you want to refer to a specific anchor in a wiki page, corresponding to a header level, that contains accentuated characters, the URL generated doesn't work. This happens whatever mean you used to create the reference to the anchor : an explicit TracLink, PageOutLine, TOC plugin…
Here is an example of such a URL: https://trac.lal.in2p3.fr/TracLAL/wiki/Admin/Install#Problèmesconnus
(should be word-public readable). This should refer to an anchor automatically created by Trac for the following header:
=== Problèmes connus ===
If replacing the è
by e
, everything works as expected.
Cheers,
Michel
Attachments (0)
Change History (6)
comment:1 by , 16 years ago
Component: | general → wiki system |
---|---|
Keywords: | needinfo added |
Milestone: | 0.11.3 |
comment:2 by , 16 years ago
The XML specification requires an ID attribute to be a Name. I suppose that accented characters fall into the "Name" definition, so it should work.
comment:3 by , 16 years ago
I use Opera (9.63). I was sure I tested in IE7 too but it was probably just a dream ! I tested again and it works. I'll fill a bug against Opera. Thanks. You can probably close this ticket.
Michel
comment:4 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:5 by , 16 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
comment:6 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
Please don't do that.
Your example worked for me in Chrome, IE 7 and Firefox 3.0.3, but not in Opera 9.63 (all versions tested on Windows). Which browser did you use?
Not sure if it's a browser bug or if Chrome, IE7 and FF3 worked "by chance". In the latter case we might do something.