Re: [translations] Changes section in stable

[Francisco Vila]

El 10/3/20 a las 10:36, Phil Holmes escribió:


It's not an obscure manual process, it's an obscure automatic process.  
I built 2.20 with GUB, uploaded it with GUB and it automatically created 
the "stable" docs and opposed to the unstable ones.



I have just built docs from stable branch and Manuals page says "Manuals 
for LilyPond 2.20.0". Then I go to  Community/Development and it says 
"Development for LilyPond 2.20.0" as well. So it is still a bit obscure 
to me, how the online web hosts a mix of stable and devel, which branch 
is it built from?


--
Francisco Vila, Ph.D. - Badajoz (Spain)
paconet.org , lilypond.es

Re: [translations] Changes section in stable

[Phil Holmes]

- Original Message - 
From: "Francisco Vila" 
To: "David Kastrup" ; "Jean-Charles Malahieude" 

Cc: "Translations list at lilynet" ; 
"LilyPond-Devel list" 

Sent: Monday, March 09, 2020 7:55 PM
Subject: Re: [translations] Changes section in stable



El 9/3/20 a las 20:37, David Kastrup escribió:

Jean-Charles Malahieude  writes:


Le 09/03/2020 à 18:21, Francisco Vila a écrit :

Anyway. I expected wrongly to see translated es/changes showing
online, but this will only happpen when the second stable minor
version occurrs. Right?



Wrong! translation has to be merged into master and then the website
regenerated.


I think Francisco is talking about 2.18–2.20 changes, not 2.20–2.22
changes.


True, the latter is devel- , but devel now in the page is 2.19 (= future 
2.20) so changes page in devel section is still "2.20 since 2.18".


404 also for me in http://lilypond.org/website/development.es.html BTW.


I really have no clue just when and how the _stable_
documentation makes it into our web pages.


Mmm, tricky. It shouldn't be an obscure manual process.




It's not an obscure manual process, it's an obscure automatic process.  I 
built 2.20 with GUB, uploaded it with GUB and it automatically created the 
"stable" docs and opposed to the unstable ones.


--
Phil Holmes 

Re: [translations] Changes section in stable

[Francisco Vila]

El 9/3/20 a las 20:37, David Kastrup escribió:

Jean-Charles Malahieude  writes:


Le 09/03/2020 à 18:21, Francisco Vila a écrit :

Anyway. I expected wrongly to see translated es/changes showing
online, but this will only happpen when the second stable minor
version occurrs. Right?



Wrong! translation has to be merged into master and then the website
regenerated.


I think Francisco is talking about 2.18–2.20 changes, not 2.20–2.22
changes. 


True, the latter is devel- , but devel now in the page is 2.19 (= future 
2.20) so changes page in devel section is still "2.20 since 2.18".


404 also for me in http://lilypond.org/website/development.es.html BTW.


I really have no clue just when and how the _stable_
documentation makes it into our web pages.


Mmm, tricky. It shouldn't be an obscure manual process.


--
Francisco Vila, Ph.D. - Badajoz (Spain)
paconet.org , lilypond.es

Re: [translations] Changes section in stable

[David Kastrup]

Jean-Charles Malahieude  writes:

> Le 09/03/2020 à 18:21, Francisco Vila a écrit :
>> Anyway. I expected wrongly to see translated es/changes showing
>> online, but this will only happpen when the second stable minor
>> version occurrs. Right?
>> 
>
> Wrong! translation has to be merged into master and then the website
> regenerated.

I think Francisco is talking about 2.18–2.20 changes, not 2.20–2.22
changes.  I really have no clue just when and how the _stable_
documentation makes it into our web pages.

-- 
David Kastrup

Re: [translations] Changes section in stable

[Jean-Charles Malahieude]

Le 09/03/2020 à 18:21, Francisco Vila a écrit :

Anyway. I expected wrongly to see translated es/changes showing
online, but this will only happpen when the second stable minor
version occurrs. Right?



Wrong! translation has to be merged into master and then the website 
regenerated.


And I'm about to first merge master into translation (you'll have one 
more item in changes.tely BTW).


Cheers
--
Jean-Charles

Re: [translations] Changes section in stable

[Francisco Vila]

El 8/3/20 a las 21:04, David Kastrup escribió:

In the translations, the links need to get redirected to
language-specific versions.  Depending on the language, Partly this
happens by changing the macros creating the documentation links (I think
that should likely be the most sensible way), partly it happens by
changing the_invocations_  of those macros,


Generated file Documentation/LL/out-www/weblinks.itexi is identical for 
all LL languages, so one could think the difference must rely only on 
choosing the right incovation. But on second thougth, the macros 
themselves could still be wrong, because different languages use 
different macros.


Anyway. I expected wrongly to see translated es/changes showing online, 
but this will only happpen when the second stable minor version occurrs. 
Right?


--
Francisco Vila, Ph.D. - Badajoz (Spain)
paconet.org , lilypond.es

Re: [translations] Changes section in stable

[David Kastrup]

Francisco Vila  writes:

> Hello, regarding to changes section in Stable, now online:
>
> English looks perfect, obviously.
>
> Links in Català give 404
>
> cs, de, fr, hu, zh, nl, and ja links lead to English version
>
> Spanish Split gives 404, Bigpage leads to an empty (titled) page and
> PDF link leads to a empty (titled) PDF. Sources are translated.
>
> Italiano looks perfect. As in English, Split and Bigpage look the same
> because there is no sectioning in the original.
>
> I'll investigate this now.

I think that the diagnostics produced at the end of make doc by issue
 would help a
_whole_ lot with that investigation.

At least as long as you take care to keep the size calculation macros
@docSize in sync with the documentation cross references via @docLinks
et al.

In the translations, the links need to get redirected to
language-specific versions.  Depending on the language, Partly this
happens by changing the macros creating the documentation links (I think
that should likely be the most sensible way), partly it happens by
changing the _invocations_ of those macros, and partly it happens half
by accident, namely the link being formally for an English version and
the translator not noticing it because their browser preferences and the
settings of the Apache web server combine to deliver a nationalised
version instead.

If you change the invocations of the macros, the size calculations of
issue 5822 will work out of the box, but I doubt that is the best way.

I was leary about having issue 5822 go into master, but I think we are
not likely doing ourselves a favor by not doing so: it corrects some
problems and fingerpoints a number of other problems pretty well.  What
problems with doing the actual website may remain, is hard to diagnose
without seeing the actual website.  But the worst damage that can happen
to the web site is that the out-of-date size specs disappear temporarily
for links that are currently dead, or at least only visible due to
browser language settings.

-- 
David Kastrup