[CONTTAGS-69] No support of special characters Created: 02/Aug/18 Updated: 18/Aug/23 |
|
| Status: | Open |
| Project: | Content Tags |
| Component/s: | None |
| Affects Version/s: | 1.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Frank Sommer | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Team: | |||||||||
| Description |
|
Using tags with special characters like 'égalité' isn't possible. These characters will replaced by a dash. The result is -galit- |
| Comments |
| Comment by Roman Kovařík [ 02/Aug/18 ] |
|
Same with UTF-8? |
| Comment by Frank Sommer [ 11/Jan/19 ] |
|
To enable global UTF-8 node name support is not a good idea just for this bug. Because you will get a lot of encoding trouble on path handling and url creation. |
| Comment by Richard Gange [ 17/Aug/23 ] |
|
Working on 6.2.37 |
| Comment by Frank Sommer [ 18/Aug/23 ] |
|
It works only with global UTF-8 support for node names. But I think that isn't a good idea like my comment before said. |
| Comment by Richard Gange [ 18/Aug/23 ] |
|
Hi Frank- Sorry yes I see. I guess the problem is the tags are saved as nodes. Without UTF-8 enabled then you cannot save nodes with special characters. BR |