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

Re: more missing DLAs on the website

Am 02.04.19 um 12:39 schrieb Sylvain Beucler:
> Hi,
> On 02/04/2019 12:09, Holger Levsen wrote:
>> On Tue, Apr 02, 2019 at 11:52:58AM +0200, Sylvain Beucler wrote:
>>> OK so I guess we need DLA translations ;)
>>> I was wondered whether actual users asked for them, but let's assume so.
>> you might not be aware, but:
>> ~/Projects/debian-www/webwml$ for i in english french russian danish japanese ; do echo -n "$i: " ; find |grep -i dla|grep -c $i ; done
>> english: 3574
>> french: 703
>> russian: 424
>> danish: 73
>> japanese: 108
> That's precisely what I'm worried about: we're taking resources from
> translators (and for quite boring texts), so I hope users do care about it.
> I don't see security advisory translations in other distros, so we
> better be confident this is worth the effort - including our effort to
> double-publish DLAs at the website :)

First of all, thank you for your improvements on the parse script. I
share your concerns about the usefulness of translating the security
advisories. I agree without the translations we could also consider to
link to the mail archive.

>>>> https://salsa.debian.org/webmaster-team/webwml/merge_requests/47
>>> Cool, though we still have the parse-dla limitations, i.e. the results
>>> needs to be manually checked every time.
>> yup. and besides #859123 there is also #922246: "www/lts: if DLA-1234-1 and 
>> DLA-1234-2 exist, only that last one shows up in indexes"
>>> It seems implicit given my involvement in the discussions and fixes for
>>> the past weeks, but I'm willing to help improve this too :)
>> yay. please just go ahead. ;)
> One issue is that I proposed to simplify the handling of parse-dla to
> make is more robust (grab DLA description as a <pre> block instead of
> the fragile regexp-based HTMLization)
>  - but no involved parties answer.
> I'll let some time pass, then I guess I'll make the change and see who
> complains :P
> Ideally we could then cron this out as Markus suggested.

So far I had no problems with the parse script. I just download the html
file from the DLA announcement manually and then I use the script. The
idea to use a <pre> block would certainly simplify the parsing though.



Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: