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

Re: Installation guide is not updated in some languages

Samuel Thibault, on lun. 19 juin 2017 23:16:09 +0200, wrote:
> Cyril Brulebois, on dim. 18 juin 2017 16:05:25 +0200, wrote:
> > Samuel Thibault <sthibault@debian.org> (2017-06-16):
> > > Paul Wise, on mer. 14 juin 2017 11:02:11 +0800, wrote:
> > > > > (and it's not only a question of file renaming, links in the .html
> > > > > files need to be updated accordingly).
> > > > 
> > > > That would be the main issue.
> > > 
> > > Or not: we can simply change the rules that produce .html.en into
> > > producing .en.html, and drop the rules which produce .html
> > 
> > I didn't check yet, but do we have different contents in .html and
> > .CC.html?
> I guess in my earlier mail I failed to be clear: AFAICT, the name of the
> file (and thus the links) seem to be about the only change.

The buildweb.sh script is basically just forcing 

export official_build="1" (which is set for package upload anyway)
export web_build="1"
export manual_target="for_wdo"

The only differences are

- these links on the website:

    example preconfiguration file from <span class="phrase"><a class="ulink" href="http://www.debian.org/releases/stretch/example-preseed.txt"; target="_top">http://www.debian.org/releases/stretch/example-preseed.txt</a></span>.

which are made

    example preconfiguration file from <span class="phrase"><a class="ulink" href="../example-preseed.txt" target="_top">../example-preseed.txt</a></span>.

in the package. I'd say we can use relative links on the website as

- the link to the various formats:

    The document you are now reading, which is the official version of the
    Installation Guide for the stretch release of Debian; available
    in <a class="ulink" href="http://www.debian.org/releases/stretch//installmanual"; target="_top">various formats and

in the website, and 

    This document you are now reading, in plain ASCII, HTML or PDF format.

    <div class="itemizedlist"><ul class="itemizedlist" type="disc">
    <li class="listitem"><p>
    <a class="ulink" href="install.en.txt" target="_top">install.en.txt</a>
    <li class="listitem"><p>
    <a class="ulink" href="install.en.html" target="_top">install.en.html</a>
    <li class="listitem"><p>
    <a class="ulink" href="install.en.pdf" target="_top">install.en.pdf</a>

in the package. The real difference is "and [various] translations".  I
don't think this is worth making a difference between the website and
the package?


Reply to: