According to https://reference.apache.org/committer/website there should be a .revision file at the root of the site, but I couldn't find it. So most probably you have to open an INFRA ticket to ask why the change in .htaccess is not having any effect. Konrad
> On 12. Oct 2017, at 13:20, Julian Sedding <jsedd...@gmail.com> wrote: > > I expected my change to cause the Content-Type header of HTML pages > being set to "text/html;charset=utf-8", which is not (yet) the case. > DO we have any way to know if a change has made it to the live site, > or looking at what Apache httpd is doing with out .htacess file? > > @Konrad: I also saw the template encoding option for jbake, but > figured that was probably not the problem. > > Regards > Julian > > On Thu, Oct 12, 2017 at 12:08 PM, Konrad Windszus <konra...@gmx.de> wrote: >> I would also be in very strong favour of not using strange escape sequences >> and instead directly use UTF-8 sources. >> I guess the default encoding for the templates is anyhow UTF-8, but we can >> also set that explicitly >> (http://jbake.org/docs/2.4.0/#default_encoding_for_templates). >> >> If we are really afraid that those characters are messed up by editors which >> assume the wrong encoding, we can enforce the encoding with >> http://www.mojohaus.org/extra-enforcer-rules/requireEncoding.html. >> >> But I strongly agree with Julian, it is 2017 and being restricted to >> US-ASCII with long escape sequences feels weird. >> Therefore +1 for WYSYWYG and UTF-8 for the templates (with the additional >> safety net of the extra-enforcer-rules). >> >> Konrad >> >>> On 12. Oct 2017, at 08:21, Julian Sedding <jsedd...@gmail.com> wrote: >>> >>> Hi Bertrand >>> >>> Fair enough, I'll leave the template as-is. Personally, I prefer UTF-8 >>> across the whole stack, in good old WYSIWYG manner ;) >>> >>> I have pushed a change only to .htaccess now. >>> >>> Regards >>> Julian >>> >>> On Wed, Oct 11, 2017 at 2:29 PM, Bertrand Delacretaz >>> <bdelacre...@apache.org> wrote: >>>> Hi Julian, >>>> >>>> On Wed, Oct 11, 2017 at 1:26 PM, Julian Sedding <jsedd...@gmail.com> wrote: >>>>> ...I'll try reverting this fix and set AddDefaultCharset utf-8 in >>>>> .htaccess instead.... >>>> >>>> IMO it's better to avoid unicode chars in code, and those templates >>>> are code so my preference is to keep \u00a9 for the copyright sign. >>>> Encoding issues can also show up when editing files so better safe >>>> than sorry. >>>> >>>> That being said, if you can add encoding settings in the right places >>>> like .htaccess that's fantastic! I just prefer keeping the code as is >>>> - belt and suspenders maybe ;-) >>>> >>>> -Bertrand >>
