On 26 March 2014 09:59, Benedikt Ritter <[email protected]> wrote:
> Sebb, you have fixed this kind of problems before. Can you give a hint on
> what to do here? I Think I remember that you changed something in SVN...

That was to ensure that commit messages used the correct encoding; it
has no effect on HTML encoding.

When I view the page, my browser says it is in UTF-8
However the file appears to be in ISO-8859-1

We need to establish what is the correct setting for the website and
ensure that all files used on the website use that setting.
This needs to be done carefully to avoid breaking code; i.e. we should
not just change the encoding in the pom without checking for ill
effects.

As a work-round for the website display, it would be easy enough to
change the file in svnpubsub tree (not sure it can be done through the
CMS).
But going forward, the file encodings need to be carefully looked at.

Maybe there is a plugin that can check text files for mismatched encodings?

> ---------- Forwarded message ----------
> From: Duncan Jones (JIRA) <[email protected]>
> Date: 2014-03-26 10:53 GMT+01:00
> Subject: [jira] [Created] (LANG-991) Release notes cannot display special
> characters
> To: [email protected]
>
>
> Duncan Jones created LANG-991:
> ---------------------------------
>
>              Summary: Release notes cannot display special characters
>                  Key: LANG-991
>                  URL: https://issues.apache.org/jira/browse/LANG-991
>              Project: Commons Lang
>           Issue Type: Bug
>           Components: Website
>     Affects Versions: 3.3.1
>             Reporter: Duncan Jones
>             Priority: Minor
>
>
> When viewing [the release notes|
> http://commons.apache.org/proper/commons-lang/release-notes/RELEASE-NOTES-3.3.1.txt]
> online, special characters in some contributors names are not showing
> correctly.
>
> E.g. search for:
>
> {noformat}
> o LANG-951:  Fragments are wrong by 1 day when using fragment YEAR or MONTH.
>              Thanks to Sebastian G�tz.
> {noformat}
>
> I'd guess we need to change the Maven resource encoding for this file,
> although I've not yet had time to poke at the problem in any great detail.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.2#6252)
>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to