lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2566fa8cfbfc89aed22d7a8d20e303a4@vaga.pv.it>
Date:   Sun, 04 Jul 2021 15:52:41 +0200
From:   Federico Vaga <federico.vaga@...a.pv.it>
To:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc:     Jonathan Corbet <corbet@....net>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        "Guilherme G. Piccoli" <gpiccoli@...onical.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Kees Cook <keescook@...omium.org>,
        Lepton Wu <ytht.net@...il.com>, Mel Gorman <mgorman@...e.de>,
        Qais Yousef <qais.yousef@....com>,
        Randy Dunlap <rdunlap@...radead.org>,
        Rasmus Villemoes <linux@...musvillemoes.dk>,
        Stephen Kitt <steve@....org>, Wang Qing <wangqing@...o.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/12] docs: accounting: update delay-accounting.rst
 reference

Hi Mauro,

and sorry for the late reply

On 2021-06-03 09:56, Mauro Carvalho Chehab wrote:
> Some manual work is needed, as a couple of replacements occurred inside
> tables. I also need to check if automarkup.py got everything, including
> the ones inside tables.
> 
> I'm in doubt with regards to translations. There, the tag is used
> to point to the original translation, like on
> Documentation/translations/it_IT/core-api/symbol-namespaces.rst:
> 
> 	:Original: :doc:`../../../core-api/symbol-namespaces`
> 	:Translator: Federico Vaga <federico.vaga@...a.pv.it>
> 
> My personal preference would be to keep using it for translations.

Why is this your preference? I would prefer to have a consistent style 
everywhere.
If ":doc:" is now discouraged, then do not use it. What am I missing?

-- 
Federico Vaga

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ