Re: search-box.ihtml not tracked by check-translation script?

[Federico Bruni]

Maybe you're right: a symlink would be better in this case.
I've just pushed other two commits. Let's see if the build works now.


Il giorno ven, dic 18 2020 at 22:39:42 +0100, Jonas Hahnfeld 
 ha scritto:
That would obviously also work, but the last update in 
Documentation/cs

seems to be
commit e593c62a665b8d3a8e095da059595301585c2163
Author: Pavel Fric 
Date:   Thu Aug 30 18:46:50 2012 +0200

Doc-cs. Update of fundamental.itely.

I had already planned to go over the state of translated manuals and
the website early next year, IMHI heavily outdated pages are worse 
than

English content.

Jonas

Am Freitag, dem 18.12.2020 um 22:32 +0100 schrieb Federico Bruni:

 Ok, thank you Jonas!

 There's a third option I like more:

 3) mandatory translation of search-box.ihtml (it's already in the 
list

 of files to be translated in the CG manual)
 I may contact the cs translator to get it translated and/or ask for
 help on lilypond-user.

 Il giorno ven, dic 18 2020 at 22:25:48 +0100, Jonas Hahnfeld
  ha scritto:
 > There's no Documentation/cs/search-box.ihtml, so IIRC lilypond-
 > texi2html.init searches for the fallback in Documentation/. Now we
 > could of course adapt this check, but this feels odd from a 
language

 > perspective. Two more ideas:
 > 1) Adapt the check-translation script
 > 2) Also add a symlink from Documentation/search-box.ihtml to
 > en/search-
 > box.ihtml.
 >
 > WDYT?
 > Jonas
 >
 > Am Freitag, dem 18.12.2020 um 21:05 + schrieb Kevin Barry:
 > >  Hi Federico,
 > >
 > >  I don't know anything about this part of the code, but the 
relevant

 > > errors
 > >  from the doc build pipeline seem to be:
 > >  no such file: search-box.ihtml: No such file or directory at
 > >  
/builds/lilypond/lilypond/Documentation/lilypond-texi2html.init line

 > >  836.
 > >  
/builds/lilypond/lilypond/build/.././Documentation/GNUmakefile:246:

 > >  recipe for target 'out-www/cs/web-big-page.html' failed
 > >
 > >  Does that point you in the right direction?
 > >
 > >  Kevin
 > >
 > >  On Fri, 18 Dec 2020 at 20:27, Federico Bruni 


 > > wrote:
 > >  >
 > >  > I've just submitted a MR:
 > >  > https://gitlab.com/lilypond/lilypond/-/merge_requests/545
 > >  >
 > >  > but it doesn't pass the doc build pipeline.
 > >  >
 > >  > It worked for me on my computer, even though only english 
docs

 > > were
 > >  > built.
 > >  > Basically I just added 'en' to the LY_LANGUAGES variable 
before

 > > the
 > >  > other languages are appended.
 > >  >
 > >  > Any advice is welcomed! :-)
 > >  >
 > >  >
 > >  >
 > >  > Il giorno mer, dic 9 2020 at 00:38:05 +0100, Federico Bruni
 > >  >  ha scritto:
 > >  > > Any reason why search-box.ihtml is in Documentation/ 
instead of

 > >  > > Documentation/en?
 > >  > > It seems it's causing troubles to the check-translation 
script:

 > >  > >
 > >  > > $ cd Documentation
 > >  > > $ make ISOLANG=fr check-translation | grep 'diff --git'
 > >  > > warning: fr/search-box.ihtml: 128 fatal: path
 > >  > > 'Documentation/en/search-box.ihtml' does not exist in 
'HEAD'

 > >  > >
 > >  > >
 > >  > >
 > >  >
 > >  >
 > >  >
 > >
 >

Re: search-box.ihtml not tracked by check-translation script?

[Jonas Hahnfeld via Discussions on LilyPond development]

That would obviously also work, but the last update in Documentation/cs
seems to be
commit e593c62a665b8d3a8e095da059595301585c2163
Author: Pavel Fric 
Date:   Thu Aug 30 18:46:50 2012 +0200

Doc-cs. Update of fundamental.itely.

I had already planned to go over the state of translated manuals and
the website early next year, IMHI heavily outdated pages are worse than
English content.

Jonas

Am Freitag, dem 18.12.2020 um 22:32 +0100 schrieb Federico Bruni:
> Ok, thank you Jonas!
> 
> There's a third option I like more:
> 
> 3) mandatory translation of search-box.ihtml (it's already in the list 
> of files to be translated in the CG manual)
> I may contact the cs translator to get it translated and/or ask for 
> help on lilypond-user.
> 
> Il giorno ven, dic 18 2020 at 22:25:48 +0100, Jonas Hahnfeld 
>  ha scritto:
> > There's no Documentation/cs/search-box.ihtml, so IIRC lilypond-
> > texi2html.init searches for the fallback in Documentation/. Now we
> > could of course adapt this check, but this feels odd from a language
> > perspective. Two more ideas:
> > 1) Adapt the check-translation script
> > 2) Also add a symlink from Documentation/search-box.ihtml to 
> > en/search-
> > box.ihtml.
> > 
> > WDYT?
> > Jonas
> > 
> > Am Freitag, dem 18.12.2020 um 21:05 + schrieb Kevin Barry:
> > >  Hi Federico,
> > > 
> > >  I don't know anything about this part of the code, but the relevant 
> > > errors
> > >  from the doc build pipeline seem to be:
> > >  no such file: search-box.ihtml: No such file or directory at
> > >  /builds/lilypond/lilypond/Documentation/lilypond-texi2html.init line
> > >  836.
> > >  /builds/lilypond/lilypond/build/.././Documentation/GNUmakefile:246:
> > >  recipe for target 'out-www/cs/web-big-page.html' failed
> > > 
> > >  Does that point you in the right direction?
> > > 
> > >  Kevin
> > > 
> > >  On Fri, 18 Dec 2020 at 20:27, Federico Bruni  
> > > wrote:
> > >  >
> > >  > I've just submitted a MR:
> > >  > https://gitlab.com/lilypond/lilypond/-/merge_requests/545
> > >  >
> > >  > but it doesn't pass the doc build pipeline.
> > >  >
> > >  > It worked for me on my computer, even though only english docs 
> > > were
> > >  > built.
> > >  > Basically I just added 'en' to the LY_LANGUAGES variable before 
> > > the
> > >  > other languages are appended.
> > >  >
> > >  > Any advice is welcomed! :-)
> > >  >
> > >  >
> > >  >
> > >  > Il giorno mer, dic 9 2020 at 00:38:05 +0100, Federico Bruni
> > >  >  ha scritto:
> > >  > > Any reason why search-box.ihtml is in Documentation/ instead of
> > >  > > Documentation/en?
> > >  > > It seems it's causing troubles to the check-translation script:
> > >  > >
> > >  > > $ cd Documentation
> > >  > > $ make ISOLANG=fr check-translation | grep 'diff --git'
> > >  > > warning: fr/search-box.ihtml: 128 fatal: path
> > >  > > 'Documentation/en/search-box.ihtml' does not exist in 'HEAD'
> > >  > >
> > >  > >
> > >  > >
> > >  >
> > >  >
> > >  >
> > > 
> > 
> 
> 



signature.asc
Description: This is a digitally signed message part

Re: search-box.ihtml not tracked by check-translation script?

[Federico Bruni]

Ok, thank you Jonas!

There's a third option I like more:

3) mandatory translation of search-box.ihtml (it's already in the list 
of files to be translated in the CG manual)
I may contact the cs translator to get it translated and/or ask for 
help on lilypond-user.


Il giorno ven, dic 18 2020 at 22:25:48 +0100, Jonas Hahnfeld 
 ha scritto:

There's no Documentation/cs/search-box.ihtml, so IIRC lilypond-
texi2html.init searches for the fallback in Documentation/. Now we
could of course adapt this check, but this feels odd from a language
perspective. Two more ideas:
1) Adapt the check-translation script
2) Also add a symlink from Documentation/search-box.ihtml to 
en/search-

box.ihtml.

WDYT?
Jonas

Am Freitag, dem 18.12.2020 um 21:05 + schrieb Kevin Barry:

 Hi Federico,

 I don't know anything about this part of the code, but the relevant 
errors

 from the doc build pipeline seem to be:
 no such file: search-box.ihtml: No such file or directory at
 /builds/lilypond/lilypond/Documentation/lilypond-texi2html.init line
 836.
 /builds/lilypond/lilypond/build/.././Documentation/GNUmakefile:246:
 recipe for target 'out-www/cs/web-big-page.html' failed

 Does that point you in the right direction?

 Kevin

 On Fri, 18 Dec 2020 at 20:27, Federico Bruni  
wrote:

 >
 > I've just submitted a MR:
 > https://gitlab.com/lilypond/lilypond/-/merge_requests/545
 >
 > but it doesn't pass the doc build pipeline.
 >
 > It worked for me on my computer, even though only english docs 
were

 > built.
 > Basically I just added 'en' to the LY_LANGUAGES variable before 
the

 > other languages are appended.
 >
 > Any advice is welcomed! :-)
 >
 >
 >
 > Il giorno mer, dic 9 2020 at 00:38:05 +0100, Federico Bruni
 >  ha scritto:
 > > Any reason why search-box.ihtml is in Documentation/ instead of
 > > Documentation/en?
 > > It seems it's causing troubles to the check-translation script:
 > >
 > > $ cd Documentation
 > > $ make ISOLANG=fr check-translation | grep 'diff --git'
 > > warning: fr/search-box.ihtml: 128 fatal: path
 > > 'Documentation/en/search-box.ihtml' does not exist in 'HEAD'
 > >
 > >
 > >
 >
 >
 >

Re: search-box.ihtml not tracked by check-translation script?

[Jonas Hahnfeld]

There's no Documentation/cs/search-box.ihtml, so IIRC lilypond-
texi2html.init searches for the fallback in Documentation/. Now we
could of course adapt this check, but this feels odd from a language
perspective. Two more ideas:
1) Adapt the check-translation script
2) Also add a symlink from Documentation/search-box.ihtml to en/search-
box.ihtml.

WDYT?
Jonas

Am Freitag, dem 18.12.2020 um 21:05 + schrieb Kevin Barry:
> Hi Federico,
> 
> I don't know anything about this part of the code, but the relevant errors
> from the doc build pipeline seem to be:
> no such file: search-box.ihtml: No such file or directory at
> /builds/lilypond/lilypond/Documentation/lilypond-texi2html.init line
> 836.
> /builds/lilypond/lilypond/build/.././Documentation/GNUmakefile:246:
> recipe for target 'out-www/cs/web-big-page.html' failed
> 
> Does that point you in the right direction?
> 
> Kevin
> 
> On Fri, 18 Dec 2020 at 20:27, Federico Bruni  wrote:
> > 
> > I've just submitted a MR:
> > https://gitlab.com/lilypond/lilypond/-/merge_requests/545
> > 
> > but it doesn't pass the doc build pipeline.
> > 
> > It worked for me on my computer, even though only english docs were
> > built.
> > Basically I just added 'en' to the LY_LANGUAGES variable before the
> > other languages are appended.
> > 
> > Any advice is welcomed! :-)
> > 
> > 
> > 
> > Il giorno mer, dic 9 2020 at 00:38:05 +0100, Federico Bruni
> >  ha scritto:
> > > Any reason why search-box.ihtml is in Documentation/ instead of
> > > Documentation/en?
> > > It seems it's causing troubles to the check-translation script:
> > > 
> > > $ cd Documentation
> > > $ make ISOLANG=fr check-translation | grep 'diff --git'
> > > warning: fr/search-box.ihtml: 128 fatal: path
> > > 'Documentation/en/search-box.ihtml' does not exist in 'HEAD'
> > > 
> > > 
> > > 
> > 
> > 
> > 
> 



signature.asc
Description: This is a digitally signed message part

Re: search-box.ihtml not tracked by check-translation script?

[Kevin Barry]

Hi Federico,

I don't know anything about this part of the code, but the relevant errors
from the doc build pipeline seem to be:
no such file: search-box.ihtml: No such file or directory at
/builds/lilypond/lilypond/Documentation/lilypond-texi2html.init line
836.
/builds/lilypond/lilypond/build/.././Documentation/GNUmakefile:246:
recipe for target 'out-www/cs/web-big-page.html' failed

Does that point you in the right direction?

Kevin

On Fri, 18 Dec 2020 at 20:27, Federico Bruni  wrote:
>
> I've just submitted a MR:
> https://gitlab.com/lilypond/lilypond/-/merge_requests/545
>
> but it doesn't pass the doc build pipeline.
>
> It worked for me on my computer, even though only english docs were
> built.
> Basically I just added 'en' to the LY_LANGUAGES variable before the
> other languages are appended.
>
> Any advice is welcomed! :-)
>
>
>
> Il giorno mer, dic 9 2020 at 00:38:05 +0100, Federico Bruni
>  ha scritto:
> > Any reason why search-box.ihtml is in Documentation/ instead of
> > Documentation/en?
> > It seems it's causing troubles to the check-translation script:
> >
> > $ cd Documentation
> > $ make ISOLANG=fr check-translation | grep 'diff --git'
> > warning: fr/search-box.ihtml: 128 fatal: path
> > 'Documentation/en/search-box.ihtml' does not exist in 'HEAD'
> >
> >
> >
>
>
>

Re: search-box.ihtml not tracked by check-translation script?

[Dan Eble]

On Dec 18, 2020, at 15:26, Federico Bruni  wrote:
> 
> I've just submitted a MR:
> https://gitlab.com/lilypond/lilypond/-/merge_requests/545
> 
> but it doesn't pass the doc build pipeline.
> 
> It worked for me on my computer, even though only english docs were built.
> Basically I just added 'en' to the LY_LANGUAGES variable before the other 
> languages are appended.
> 
> Any advice is welcomed! :-)

I applied your patch over master and I hit the same problem as the CI when I 
ran make -j7 CPU_COUNT=7 doc.
— 
Dan

Re: search-box.ihtml not tracked by check-translation script?

[Federico Bruni]

I've just submitted a MR:
https://gitlab.com/lilypond/lilypond/-/merge_requests/545

but it doesn't pass the doc build pipeline.

It worked for me on my computer, even though only english docs were 
built.
Basically I just added 'en' to the LY_LANGUAGES variable before the 
other languages are appended.


Any advice is welcomed! :-)



Il giorno mer, dic 9 2020 at 00:38:05 +0100, Federico Bruni 
 ha scritto:
Any reason why search-box.ihtml is in Documentation/ instead of 
Documentation/en?

It seems it's causing troubles to the check-translation script:

$ cd Documentation
$ make ISOLANG=fr check-translation | grep 'diff --git'
warning: fr/search-box.ihtml: 128 fatal: path 
'Documentation/en/search-box.ihtml' does not exist in 'HEAD'

Re: state of the ’Pond for earnest tadpoles

[Jonas Hahnfeld]

Hi Kieren,

I would claim that the contributor experience has been pretty stable
since the initial switch to GitLab. Enabling CI and the recent work to
also run 'make check' automatically shouldn't change much from a
contributor's point of view, I hope.
I can't promise to give detailed guidance, the procedures should be
described in unstable's CG, but if there's anything unclear or even
wrong I'm more than happy to help you and of course fix the docs.

Cheers
Jonas

Am Dienstag, dem 15.12.2020 um 11:25 -0500 schrieb Kieren MacMillan:
> Hello all!
> 
> I’m just wondering if the new process / repo / workflow is in a state where 
> an enthusiastic but oft-discouraged[-by-the-state-of-the-tech-and-process] 
> Frog might finally dive in fully to the contribution process?
> 
> If so, which Jedi Master(s) might patiently guide this young Padawan through 
> the setup to his first patch?
> 
> Many thanks,
> Kieren.
> 
> 
> Kieren MacMillan, composer (he/him/his)
> ‣ website: www.kierenmacmillan.info
> ‣ email: kie...@kierenmacmillan.info


signature.asc
Description: This is a digitally signed message part

Re: Welcome to Travis CI!

[Jonas Hahnfeld via Discussions on LilyPond development]

Hm, so I do use Travis at work, but I hope I didn't click anywhere I
shouldn't and this wasn't me. Does anybody have plans to use Travis?

Am Donnerstag, dem 17.12.2020 um 11:26 + schrieb Travis CI:
>    =  Welcome to Travis CI, GNU
> LilyPond (unofficial)!  =
> 
>   You are on Free. 
> 
>   You have 10,000 credits left - these will begin counting down
> automatically as soon as you run your first build. 
> 
>   You can use your credits to build on both private and open-source
> repositories using Linux, macOS, and Windows OS. 
> 
>   Use the `Sign up now` button below to sign up for a bigger plan to ensure
> the builds for your private repositories continue uninterrupted. 
> 
>   If you're building open-source public repositories and want to signup for
> an open-source plan, please contact  Travis
> CI. 
> 
>    You have 10,000 Credits left for building on Travis CI!
> 
>   To ensure uninterrupted service, sign up for a suitable plan before
> you run out of credits.
> 
>    *Note: *You must be an *owner of the account* to sign up for a
> subscription.
> 
>   SIGN UP NOW   Thank
> you and have a great day!
> 
>   *The Travis CI Team* Have
> any questions?  We're here to help. 
>  Travis CI GmbH, Rigaer Str. 8, 10427 Berlin,
> Germany | GF/CEO: Randy Jacops | Contact: cont...@travis-ci.org
>  | Amtsgericht Charlottenburg, Berlin, HRB
> 140133 B | Umsatzsteuer-ID gemäß §27 a Umsatzsteuergesetz: DE282002648



signature.asc
Description: This is a digitally signed message part

Re: A basic question of Lilypond

[Jonas Hahnfeld]

Hi,

I would guess that wyanshan talks about LilyPad which comes pre-
installed with LilyPond and opens up a welcome file IIRC, coming from
the ly/ directory in LilyPond's tree. The sources for the editor are
over here: https://github.com/gperciva/lilypad. Personally I would not
put effort into this, we should just advertise Frescobaldi which is way
better. Or just using a standard editor which syntax highlighting.

Regards
Jonas

Am Freitag, dem 18.12.2020 um 15:18 + schrieb Carl Sorensen:
> Dear wyanshan,
> 
> There is no opening window for LilyPond.  LilyPond is a text and command-line 
> based program, not a GUI-based program.
> 
> http://lilypond.org/text-input.html
> 
> Some people have written GUI applications that do the work of running the 
> command-line based lilypond executable:
> 
> http://lilypond.org/easier-editing.html
> 
> Personally, I prefer Frescobaldi.
> 
> From your emails, I'm not sure what you are trying to do, so I don't know how 
> to help you better.
> 
> Best wishes,
> 
> Carl 
> 
> On 12/18/20, 1:12 AM, "lilypond-devel on behalf of wyanshan" 
>  wyans...@163.com> wrote:
> 
> Hello everyone, 
> 
> 
> I start to learn C++ programming half years ago and have just a little 
> programming experiences before that.
> I  played guitar in my free time and know basic theory of music. I found 
> LilyPond!
> 
> 
> I have a very basic question about lilypond, maybe basic, but I think 
> basic questions and answers would be to way for those who want to open a door 
> of a new world. Thanks ahead.
> 
> 
> Where is the start up window file is in the source code? (The start up 
> window means the window when you open the software). For example with excel 
> VBA, I create a window file named with myWindow.frm,
> So the my Window.frm (with extension name frm) is saved, I can find it.  
> I think I have downloaded the source file I can find lilyPond GUI design file 
> and the scheme of this window loading process, and also design of menus, I 
> tried
> But I can’t find it.   
> So, would some friend teach me the lilyPond software startup theory and 
> how to design the GUI look.
> 
> 
> Fortunatelly, I found the Untitled file is in the directory of ‘ly’ with 
> file name welcome-to-LilyPond-MACOS.ly 
> , which means I am not very foolish.
> 
> 
> I really suggest there should be a very basic manual telling programming 
> beginners the very basic software startup theory and GUI design and the inter 
> relationship among the sourcecode.
> Maybe you think these things is too basic, but I think this is import...
> 
> 
> 
> 
> 



signature.asc
Description: This is a digitally signed message part

Re: A basic question of Lilypond

[Carl Sorensen]

Dear wyanshan,

There is no opening window for LilyPond.  LilyPond is a text and command-line 
based program, not a GUI-based program.

http://lilypond.org/text-input.html

Some people have written GUI applications that do the work of running the 
command-line based lilypond executable:

http://lilypond.org/easier-editing.html

Personally, I prefer Frescobaldi.

From your emails, I'm not sure what you are trying to do, so I don't know how 
to help you better.

Best wishes,

Carl 

On 12/18/20, 1:12 AM, "lilypond-devel on behalf of wyanshan" 
 wrote:

Hello everyone, 

I start to learn C++ programming half years ago and have just a little 
programming experiences before that.
I  played guitar in my free time and know basic theory of music. I found 
LilyPond!

I have a very basic question about lilypond, maybe basic, but I think basic 
questions and answers would be to way for those who want to open a door of a 
new world. Thanks ahead.

Where is the start up window file is in the source code? (The start up 
window means the window when you open the software). For example with excel 
VBA, I create a window file named with myWindow.frm,
So the my Window.frm (with extension name frm) is saved, I can find it.  I 
think I have downloaded the source file I can find lilyPond GUI design file and 
the scheme of this window loading process, and also design of menus, I tried
But I can’t find it.   
So, would some friend teach me the lilyPond software startup theory and how 
to design the GUI look.

Fortunatelly, I found the Untitled file is in the directory of ‘ly’ with 
file name welcome-to-LilyPond-MACOS.ly , 
which means I am not very foolish.

I really suggest there should be a very basic manual telling programming 
beginners the very basic software startup theory and GUI design and the inter 
relationship among the sourcecode.
Maybe you think these things is too basic, but I think this is import...

PATCHES - Countdown for December 18th

[James Lowe]

Hello,

Here is the current patch countdown list. The next countdown will be on 
December 20th


A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority


 Push:

No patches in Countdown at this time.


 Countdown:

No patches in Countdown at this time.


 Review:

No patches in Review at this time.


 New:

No patches in New at this time.


 Waiting:

No patches in Waiting at this time.


***


Regards,

James

Re: A basic question of Lilypond

[David Kastrup]

wyanshan  writes:

> Hello everyone, 
>
> I start to learn C++ programming half years ago and have just a little
> programming experiences before that.
> I  played guitar in my free time and know basic theory of music. I found 
> LilyPond!
>
> I have a very basic question about lilypond, maybe basic, but I think
> basic questions and answers would be to way for those who want to open
> a door of a new world. Thanks ahead.

That sounds more like a question for the user list than the developer list.

> Where is the start up window file is in the source code? (The start up
> window means the window when you open the software). For example with
> excel VBA, I create a window file named with myWindow.frm,
> So the my Window.frm (with extension name frm) is saved, I can find
> it.  I think I have downloaded the source file I can find lilyPond GUI
> design file and the scheme of this window loading process, and also
> design of menus, I tried
> But I can’t find it.   
> So, would some friend teach me the lilyPond software startup theory
> and how to design the GUI look.

 should explain that.  Then there
is .

You say you program in C++.  Where is the startup file for C++?  There
is no such thing, but there are various IDEs you can use for writing C++
code.  Similar with LilyPond.  Frescobaldi is a pretty popular one.

-- 
David Kastrup

A basic question of Lilypond

[wyanshan]

Hello everyone, 

I start to learn C++ programming half years ago and have just a little 
programming experiences before that.
I  played guitar in my free time and know basic theory of music. I found 
LilyPond!

I have a very basic question about lilypond, maybe basic, but I think basic 
questions and answers would be to way for those who want to open a door of a 
new world. Thanks ahead.

Where is the start up window file is in the source code? (The start up window 
means the window when you open the software). For example with excel VBA, I 
create a window file named with myWindow.frm,
So the my Window.frm (with extension name frm) is saved, I can find it.  I 
think I have downloaded the source file I can find lilyPond GUI design file and 
the scheme of this window loading process, and also design of menus, I tried
But I can’t find it.   
So, would some friend teach me the lilyPond software startup theory and how to 
design the GUI look.

Fortunatelly, I found the Untitled file is in the directory of ‘ly’ with file 
name welcome-to-LilyPond-MACOS.ly , which 
means I am not very foolish.

I really suggest there should be a very basic manual telling programming 
beginners the very basic software startup theory and GUI design and the inter 
relationship among the sourcecode.
Maybe you think these things is too basic, but I think this is import...