• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Try charset="utf=8" and an acronym topic.

BTW, why use utf-8? To support copy-past from websites into TWiki topics without having curly quotes converted to question marks.


I don't understand the first line, or what the bug is - where are you setting this, in the GET URL or something? Please give an example of the problem, ideally attaching the topic .txt to this report - see TWiki:Support.SupportGuidelines for hints on reporting I18N bugs.

Generally, setting %CHARSET% is a mistake and should not be necessary. You just need to set a locale ending in .utf8 if that's what you want to use - however, as discussed in the TWiki web docs, it's really only a good idea to use UTF-8 if you are using Chinese, Japanese or some other double-byte language, where UTF-8 is the only safe encoding and the loss of WikiWord I18N is not an issue.

Enabling copy-paste from other websites is a good idea but it means forgoing a lot of I18N support if you need I18N of WikiWords.


I changed the charset in configure, at {Site}{CharSet}.

Do you mean I should set this: en_US.utf8 ?


You should set {Site}{Locale} in configure to en_US.utf8 - the {Site}{CharSet} is only there as an override for some unusual cases (e.g. charset is spelt differently in the locale from the spelling acceptable in HTTP headers for use by browser).

See TWiki:TWiki.InstallationWithI18N and please update that if parts are unclear - there's a bit under troubleshooting saying not to set the CHARSET var, maybe you could do a similar bit for {Site}{CharSet}?

Also, curly quotes are often a Windows-1252 character set peculiarity - going UTF-8 is a bit radical just for that.

  • UPDATE: For your site, you could just set the locale to use ISO-8859-1 and then set {Site}{CharSet} to Windows-1252 so that Windows-based browsers don't convert the Windows-1252 only characters (e.g. quotes) to NCRs. This is probably the simplest solution all round.

If it would be OK to convert them to normal ASCII double/single quotes (i.e. " and '), it would be a useful feature to recognise the numeric character reference and convert them. There's some code out there that's similar - maybe Google:demoroniser?

TWiki support for UTF-8 is very limited, no WikiWord autolinking of I18N characters for example - however, if you are using it in English only you will be OK.

Have set this to Discarded since this is not a bug (except perhaps in docs).


Summary TOC is broken with charset="utf=8" and topic links to itself
ReportedBy TWiki:Main.ArthurClemens

SVN Range Mon, 05 Jun 2006 build 10479
AppliesTo Engine

Priority Normal
CurrentState No Action Required


TargetRelease n/a
Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r8 - 2006-10-11 - RichardDonkin
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback