[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#762051: marked as done (translations.txt: publish it properly (announced as utf-8))

Your message dated Sat, 9 May 2015 02:41:11 +0200
with message-id <20150509004111.GN2070@mraw.org>
and subject line Re: Bug#762051: translations.txt: publish it properly (announced as utf-8)
has caused the Debian Bug report #762051,
regarding translations.txt: publish it properly (announced as utf-8)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
762051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762051
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: d-i.debian.org
Severity: normal

Since translations.txt support was added to dillon's crontab, it failed
to be announced as utf-8 so copying-pasting from a browser doesn't work:

  http://d-i.debian.org/translations.txt

It'd be nice if it could be announced properly.

Mraw,
KiBi.

--- End Message ---
--- Begin Message --- 
Cyril Brulebois <kibi@debian.org> (2014-09-18):
> Package: d-i.debian.org
> Severity: normal
> 
> Since translations.txt support was added to dillon's crontab, it failed
> to be announced as utf-8 so copying-pasting from a browser doesn't work:
> 
>   http://d-i.debian.org/translations.txt
> 
> It'd be nice if it could be announced properly.

It seems the current setup lets us specify some directives in .htaccess,
making it possible to associate UTF-8 with .txt files. I've removed the
said .htaccess (I've created manually as a first step), and added a
script which (1) updates /static from the www-static directory and (2)
creates .htaccess when needed.

This means we shouldn't have to do that manually again in case stuff is
moved to another box and/or recreated from scratch.

SVN revisions for this change: 69891 69892 69893 69894

If everything goes correctly, we should (still) get this after the next
update has happened:
  Content-Type: text/plain; charset=utf-8

(In case that breaks, we could of course wrap that inside a <pre> of an
HTML file announced as UTF-8 through a meta tag, but that's ugly…)

Christian, please yell if you see encoding-related issues in the future.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: