Re: lilypond.org now serving HTTPS

2020-02-21 Thread Federico Bruni




Il giorno ven 21 feb 2020 alle 16:18, Han-Wen Nienhuys 
 ha scritto:
On Fri, Feb 21, 2020 at 3:32 PM Federico Bruni  
wrote:


 Il giorno ven 21 feb 2020 alle 00:01, Han-Wen Nienhuys
  ha scritto:
 > The translated pages still have mixed mode data. Is it OK to edit
 > these directly in the source tree, or will that upset our 
translation

 > infrastructure?

 Which files are you going to change?



The search box ihtml

from the looks of it, it's not actually translated, as it has no 
version string.




It is translated:

$ find Documentation/ -name 'search-box.ihtml'
Documentation/hu/search-box.ihtml
Documentation/fr/search-box.ihtml
Documentation/zh/search-box.ihtml
Documentation/ja/search-box.ihtml
Documentation/search-box.ihtml
Documentation/ca/search-box.ihtml
Documentation/es/search-box.ihtml
Documentation/pt/search-box.ihtml
Documentation/it/search-box.ihtml
Documentation/de/search-box.ihtml
Documentation/nl/search-box.ihtml







Re: lilypond.org now serving HTTPS

2020-02-21 Thread Han-Wen Nienhuys
On Fri, Feb 21, 2020 at 3:32 PM Federico Bruni  wrote:
>
> Il giorno ven 21 feb 2020 alle 00:01, Han-Wen Nienhuys
>  ha scritto:
> > The translated pages still have mixed mode data. Is it OK to edit
> > these directly in the source tree, or will that upset our translation
> > infrastructure?
>
> Which files are you going to change?
>

The search box ihtml

from the looks of it, it's not actually translated, as it has no version string.

-- 
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen



Re: lilypond.org now serving HTTPS

2020-02-21 Thread Federico Bruni
Il giorno ven 21 feb 2020 alle 00:01, Han-Wen Nienhuys 
 ha scritto:

The translated pages still have mixed mode data. Is it OK to edit
these directly in the source tree, or will that upset our translation
infrastructure?


Which files are you going to change?

Consider that translators are working on the translation branch, which 
is now synced with stable/2.20 but it will be synced again with master 
after 2.20 release.







Re: lilypond.org now serving HTTPS

2020-02-20 Thread Han-Wen Nienhuys
I think the automatic update of lilypond.org has stopped working. Let
me look into it.

On Thu, Feb 20, 2020 at 10:03 PM Joram Noeck  wrote:
>
> > My browser complains about mixed content, i.e. http-linked media on the
> > page.
> >
> > Urs
>
> Here (Firefox 73), the only warning is about the "Valid HTML 4.01" image
> in the page footer. All other images (on the pages I looked at) have
> relative src attributes and are served directly from lilypond.org via https.
>
> Joram
>
>
>
> PS: Btw, the only other warning I get is about -moz-border-radius which
> was renamed to border-radius (without vendor prefix) in 2011 if I am not
> mistaken.  I also see commits that changed this in 2015¹, but perhaps
> too late for the 2.18 website? Or I don't why the latest css is not served.
>
>
> ¹:
> https://github.com/lilypond/lilypond/commit/a6f369ae2efe399ef9644a702d98187e93129a87



-- 
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen



Re: lilypond.org now serving HTTPS

2020-02-20 Thread Joram Noeck
> My browser complains about mixed content, i.e. http-linked media on the
> page.
>
> Urs

Here (Firefox 73), the only warning is about the "Valid HTML 4.01" image
in the page footer. All other images (on the pages I looked at) have
relative src attributes and are served directly from lilypond.org via https.

Joram



PS: Btw, the only other warning I get is about -moz-border-radius which
was renamed to border-radius (without vendor prefix) in 2011 if I am not
mistaken.  I also see commits that changed this in 2015¹, but perhaps
too late for the 2.18 website? Or I don't why the latest css is not served.


¹:
https://github.com/lilypond/lilypond/commit/a6f369ae2efe399ef9644a702d98187e93129a87
diff --git a/lilypond-manuals.css b/lilypond-manuals.css
index 995c217..8bff14a 100644
--- a/lilypond-manuals.css
+++ b/lilypond-manuals.css
@@ -450,9 +450,7 @@ div#search p, div#search form {
   text-align: left;
   padding: 0;
   border: 1px solid green;
-  /* Experimental rounded corners */
-  -moz-border-radius: 10px;
-  -webkit-border-radius: 10px;
+  border-radius: 10px;
   margin: 1em;
 }

@@ -461,8 +459,6 @@ div#search p, div#search form {
   text-align: left;
   padding: 0;
   border: 1px solid green;
-  /* Experimental rounded corners */
-  -moz-border-radius: 10px;
-  -webkit-border-radius: 10px;
+  border-radius: 10px;
   margin: 0.5em 0.5em 2em 3em;
 }


Re: lilypond.org now serving HTTPS

2020-02-20 Thread Urs Liska
Am Donnerstag, den 13.02.2020, 18:48 +0100 schrieb Jean-Charles
Malahieude:
> Le 13/02/2020 à 15:10, Han-Wen Nienhuys a écrit :
> > FYI, lilypond.org is now serving on HTTPS
> > 
> > See here https://codereview.appspot.com/559470043/ for background.
> > 
> 
> This should be applied on stable/2.20 as well.
> 
> Cheers,
> --
> Jean-Charles
> 

My browser complains about mixed content, i.e. http-linked media on the
page.

Urs




Re: lilypond.org now serving HTTPS

2020-02-13 Thread Jean-Charles Malahieude

Le 13/02/2020 à 15:10, Han-Wen Nienhuys a écrit :

FYI, lilypond.org is now serving on HTTPS

See here https://codereview.appspot.com/559470043/ for background.



This should be applied on stable/2.20 as well.

Cheers,
--
Jean-Charles



lilypond.org now serving HTTPS

2020-02-13 Thread Han-Wen Nienhuys
FYI, lilypond.org is now serving on HTTPS

See here https://codereview.appspot.com/559470043/ for background.

-- 
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen