Re: Broken commit IDs in French translation

Le 05/11/2022 à 18:39, Jean Abou Samra a écrit : Le 05/11/2022 à 17:26, Jean-Charles Malahieude a écrit : Le 03/11/2022 à 21:31, Jean Abou Samra a écrit : Hi Jean-Charles, What is your procedure for filling in commit IDs in translated files? It looks like a number of them don't exist

Re: Broken commit IDs in French translation

Le 03/11/2022 à 21:31, Jean Abou Samra a écrit : Hi Jean-Charles, What is your procedure for filling in commit IDs in translated files? It looks like a number of them don't exist in the repository. I either copy what is returned by "git rev-parse HEAD" or then content of the "Id SHA1"

Re: Backslashes in @warning

Le 19/10/2022 à 17:38, Werner LEMBERG a écrit : The page https://lilypond.org/doc/v2.23/Documentation/notation/writing-text.html#text-marks is missing some backslashes in the box [...] I don't immediately see what this discrepancy could be caused by, apart from a bug or limitation of

Re: RFC: disconnect from the Translation Project

Le 06/07/2022 à 20:51, Jonas Hahnfeld a écrit : ... which, as far as I understand, is processed by some form of a bot, right? At least that one message was taken care of *very* quickly... I have to confess that _I am_ the bot… until the mail announcing new releases are directly sent to the

Re: RFC: disconnect from the Translation Project

Le 06/07/2022 à 13:31, Jean Abou Samra a écrit : On 7/6/22 11:15, Werner LEMBERG wrote: The PO template that is the basis for PO files needs to be updated at every release by notifying the coordinator of the release. That's a maintenance cost.  Right now, we're not paying it, and the result is

Re: Thinking about the next stable release

Le 26/05/2022 à 18:12, Jean Abou Samra a écrit : Le 22/05/2022 à 14:39, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Hi all, with the unstable releases switched over to Guile 2.2, I think it might be a good idea to think about the next stable release. The last time, for

Re: Stepping down from Patch Meister role

Le 08/01/2022 à 12:15, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Am Samstag, dem 08.01.2022 um 10:06 + schrieb James: Hello, I am going to stop doing the Patch countdown at the end of this month. I'll continue for the next few weeks, but my last countdown will be

[Doc] Organizing changes.tely

Hello all, In the last days of 2017, just before 2.20 was born, James arranged changes.tely such that items don't get just stacked one over the other but sort of reflect the organizing of the Notation Reference. I found it very wise and useful for the reader, and kept that during the

Re: Broken make info dependencies

Le 01/10/2021 à 02:48, David Kastrup a écrit : And having to build the HTML documentation of all languages when the Info files only need the images from the English version is not exactly rewarding either. When I want to check my work in French, I first run make doc LANGS='en fr' in order

Re: [translations] Re: Working repo

Le 05/03/2021 à 15:25, Jonas Hahnfeld a écrit : Am Donnerstag, dem 04.03.2021 um 19:34 +0100 schrieb Jean-Charles Even if outside the countdown process, these MR should IMHO still be reviewed or specifically "tagged" and maybe translators prefix their own branch with Doc-LL when pending for a

Re: [translations] Re: Working repo

Le 04/03/2021 à 18:55, Jonas Hahnfeld a écrit : [...] MRs to the translation branch won't work because there are no CI pipelines defined, but I've configured GitLab to require that prior to merging. So far, we've mostly continued with the practice that translators have access to the repository

Re: Releasing 2.22.0

Le 03/01/2021 à 12:05, Jonas Hahnfeld a écrit : Hi all and happy new year 2021 to everyone! A happier new year to everyone ! As there was no real announcement for 2.20.0, I'd rather follow the release of 2.18.0 including a post to info-lilypond. Here's a first draft: OK with me for this

Re: Welcome to Travis CI!

Le 19/12/2020 à 09:58, Han-Wen Nienhuys a écrit : Am Donnerstag, dem 17.12.2020 um 11:26 + schrieb Travis CI: = Welcome to Travis CI, GNU LilyPond (unofficial)! = "GNU LilyPond (unofficial)" is the name of the Github organization for LilyPond,

Re: stable/2.22 has branched; master is 2.23.0

Le 26/10/2020 à 19:30, Jonas Hahnfeld a écrit : Yes, that !347 is quoted in commit d75b86de13 which introduced the above commit hash. As you were running translation-status in commit a2f89036bc, I suspected a rebase issue which would have kept the old commit hash for some time in your local

Re: stable/2.22 has branched; master is 2.23.0

Le 21/10/2020 à 20:12, Jonas Hahnfeld a écrit : Am Mittwoch, den 21.10.2020, 20:01 +0200 schrieb Jean-Charles Malahieude: since I'm trying to understand why snippets get translated in 2.21.7 on lilypond.org but not on my box (I've updated about 250 fr/texidocs and wanted to check how

Re: ready for 2.21.80?

Le 26/10/2020 à 12:06, Jonas Hahnfeld a écrit : […] Changing directory before invoking lilypond-book might solve this problem and help against similar issues in the future: https://gitlab.com/lilypond/lilypond/-/merge_requests/479 This looks good in preliminary testing, both with separate build

Re: ready for 2.21.80?

Le 25/10/2020 à 19:13, Jonas Hahnfeld a écrit : I can try to help if I understand the problem in detail. As you mention the NR, you're probably referring to the Selected Snippets / Morceaux choisis? The first example would be:

Re: ready for 2.21.80?

Le 25/10/2020 à 14:42, Jonas Hahnfeld a écrit : As the title says. We still need to merge the PO translations (see https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick them to stable/2.22. If you speak one of the concerned languages that I've been hijacking the translation for

Re: stable/2.22 has branched; master is 2.23.0

Le 24/10/2020 à 17:51, Jonas Hahnfeld a écrit : I just pushed a reordered version of the English changes.tely to stable/2.22, compiled HTML version attached. LGTM. BTW, your remark about skylines, the changes' entries come from different issues dealt by Torsten: commit

Re: stable/2.22 has branched; master is 2.23.0

Le 21/10/2020 à 17:35, Jonas Hahnfeld a écrit : Hi, sorry, I forgot to reply here... Am Samstag, den 17.10.2020, 10:15 +0200 schrieb Jean-Charles Malahieude: [...] > I'll appreciate anybody first checking I've not not affected a wrong category. Some things I noticed after looking at ht

Re: stable/2.22 has branched; master is 2.23.0

Le 16/10/2020 à 20:21, Jonas Hahnfeld a écrit : Am Freitag, den 16.10.2020, 20:01 +0200 schrieb Jean-Charles Malahieude: I should have finished and sent fr.po to the FTP over the week-end. I'll group the fetching once a week in a MR to master. I wonder if the translated po files should go

Re: stable/2.22 has branched; master is 2.23.0

Le 16/10/2020 à 19:41, Jonas Hahnfeld a écrit : Hi all, I created stable/2.22 as discussed and the situation is as follows: * b7c2bc5feb (origin/master) Reset Changes document for next cycle * 7f0bb931c3 Bump VERSION to 2.23.0 for next cycle | * 8a58e932f8 (origin/stable/2.22) ci: Build branch

lilypond-2.21.7

Hi, Please find a new tarball for LilyPond at http://lilypond.org/download/source/v2.21/lilypond-2.21.7.tar.gz Cheers, -- Jean-Charles Malahieude

Re: internationalized snippets

Le 13/09/2020 à 12:30, Han-Wen Nienhuys a écrit : Jean (or should I say Jean Abou?) found the following gem: https://github.com/lilypond/lilypond/blob/a2f89036bc6ed0147385ef04d1201cad3ad10fa7/python/book_snippets.py#L368 I think the problem was introduced in

Re: Side effects of MR 84 with scripts

Le 09/08/2020 à 13:12, Han-Wen Nienhuys a écrit : On Sun, Aug 9, 2020 at 12:44 PM Han-Wen Nienhuys wrote: make translation-status translations-status.py Reading documents... Generating status pages... translations-status.py:717: warning: using markup = TexiMarkup (): ugly HTML output,

Side effects of MR 84 with scripts

Hi all, I wanted to tackle updating the French version of the NR, but cd Documentation make ISOLANG=fr NO_COLOR=1 check-translation > ../../chktrans reveals that all files have been deleted. Sure! they have moved into a dedicated directory. And running translation status gives -*- mode:

Re: Access request to push to translation

Le 21/06/2020 à 13:53, Jonas Hahnfeld a écrit : Am Sonntag, den 21.06.2020, 13:20 +0200 schrieb Han-Wen Nienhuys: BTW, regarding translations: I notice that translation work gets merged as "commit cb1b3c1fb0c1d9dc1fb6fdadb0907c07b8a692e5 Merge: 22eca98efe b47e5def69 Author: Jean-Ch

convert-ly doesn't find lilylib

Hi, with master as of 15de2c8874262c2c0a9f2cc3beee5070c766dde4 $ cat buggy.ly \version "2.18.2" c1 $ ~/GIT/Mentor/out/bin/convert-ly -e TEST.ly Traceback (most recent call last): File "/home/jcharles/GIT/Mentor/out/bin/convert-ly", line 65, in import lilylib as ly ModuleNotFoundError:

Re: migrating to GitLab

Le 10/05/2020 à 10:50, Jonas Hahnfeld a écrit : Am Samstag, den 09.05.2020, 16:11 -0400 schrieb Dan Eble: On May 9, 2020, at 15:13, David Kastrup wrote: Carl Sorensen writes: ->CS At any rate, I think that we should have appropriate CG instructions at the time we make the switch. They

Re: migrating to GitLab

Le 08/05/2020 à 08:57, Jonas Hahnfeld a écrit : I haven't heard further objections which, for me, means we are going with GitLab. If you don't agree, now's your final time to speak up. Otherwise I would like to tackle the migration rather soon to take advantage of the new opportunities :-) This

Re: Annoying 'langdefs.py' warning

Le 26/04/2020 à 09:46, Jonas Hahnfeld a écrit : Am Samstag, den 25.04.2020, 21:53 +0200 schrieb Francisco Vila: El 24/4/20 a las 17:18, Jonas Hahnfeld escribió: However I'm pretty sure that many translations in the latter are dead: As far as I understand we don't translate the docs by putting

lilypond-2.21.1

Hi, Please find a new tarball for LilyPond at http://lilypond.org/download/source/v2.21/lilypond-2.21.1.tar.gz Cheers, -- Jean-Charles Malahieude

Re: Annoying 'langdefs.py' warning

Le 19/04/2020 à 16:17, Valentin Villenave a écrit : On 4/16/20, Werner LEMBERG wrote: Building lilypond you get a bunch of harmless but annoying langdefs.py: warning: lilypond-doc gettext domain not found. and .../podir-targets.make:14: warning: ignoring old recipe for target 'po-update'

Failing build

Hi, Wishing to merge back translation into master, I first want to have everything fine but, with HEAD at 2f4b432c66 framework-svg.scm: Fix 'style' tag and nothing wrong with autogen, I get make VERBOSE=1 # Making out/VERSION mkdir -p ./out echo 2.21.1 > out/VERSION # Making

Re: OT: maillist changes width, messes lines

Le 30/03/2020 à 17:31, Francisco Vila a écrit : At some point in the email path from sender to recipients, our list incorrectly word wraps some long lines. See attachment. It's in the actual email code, too. I was pretty much ignoring it until I couldn't help reading   "Anything and rather

Re: [translations] Anything missing for 2.21.0?

Le 29/03/2020 à 18:59, David Kastrup a écrit : Jean-Charles Malahieude writes: But, please, pick up the po files I mentioned (ca, da, de, eo, es, fr, it, ja, nl, sv) which are in advance on stable/2.20. As I work on local clones (one per branch), I can copy them and push onto staging

Re: [translations] Anything missing for 2.21.0?

Le 29/03/2020 à 17:54, David Kastrup a écrit : [Repeat message since I got the address of translations wrong] I see that translation-status is in master. The web site is still getting fixed (including MacOSX download links), so we'd probably better wait with the big announcements until that

Re: 2.21.0 and announcements

Le 26/03/2020 à 18:38, David Kastrup a écrit : Jean-Charles Malahieude writes: Would you mind letting me run translation-status and merge updated docs from Franscisco and myself into staging? I would not mind at all. In fact, I'd have planned to do so myself, but certainly would be glad

Re: 2.21.0 and announcements

Le 26/03/2020 à 17:11, David Kastrup a écrit : Because once the big announcements are made, we want people to actually be able to work with what they find on the web page. We can release 2.21.0 prior to that, of course, since the web page updates are (I think) independent from releases.

AU-1.2 Relocation

Hi Werner, On my way to updating the French documentation, I read in running.itely (1st item of Relocation algorithm) "Compute the directory where the currently executed @command{lilypond} binary is located. Let's call this @code{bindir}. Set (internal) environment variable

Re: make builds everything

Le 21/03/2020 à 18:11, Malte Meyn a écrit : Hi list, first of all, I’d like thank those who made the make output less verbose, this makes errors much easier to find. It is, unfortunately, sometimes too little verbose: say I've omitted a closing brace in a texinfo @-command. The only thing

Re: Upgrading to current makeinfo

Le 14/03/2020 à 21:34, Torsten Hämmerle a écrit : Apart from the fact that it's super-inelegant, you can use raw code within your @ifhtml branch to get a real superscript even in HTML, as in: … and fastidious in matter of typing,and don't forget to add a space before the next word:

Re: Upgrading to current makeinfo

Le 31/08/2019 à 21:11, Werner LEMBERG a écrit : To have both `!' and `\!' (and similar `\foo' command and `foo' property entries) in the index of the info and PDF version of the NR it is necessary to tag corresponding entries with `@sortas' directives[*]

PO: reverse from stable to master

Hi David, Would you mind cherry-picking the updated translation of po-files from stable/2.20 into master, in order for us not to redo what is up-to-date? It concerns 98c40be14709b8ca367f7940cd6d2f760f86a275 PO: fetch French and Italian from FTP 940cfe021fed3c981464c9d4bb6f0f1fbdd4ebe6 PO:

Re: translations-status.py crashes

Le 10/03/2020 à 14:50, Jonas Hahnfeld a écrit : The fix for this problem is here: https://sourceforge.net/p/testlilyissues/issues/5839/ Now in staging. Also many thanks to James for providing immediate feedback that I didn't break anything unintentionally - much appreciated! Thanks a lot.

translations-status.py crashes

Hi, Another problem with switching to Python 3: cd Documentation && make translation status crashes on branch translation (after merging master into it); it works well as expected on transaltion-staging (still on Python 2). the message is -*- mode: compilation; default-directory:

Re: Doc: organize changes.tely

Le 09/03/2020 à 19:09, David Kastrup a écrit : Francisco Vila writes: El 9/3/20 a las 11:58, David Kastrup escribió: I think I was told to run the update script and forgot. I am not sure where to run it now in order to get the results somewhere. do make translation-status from

Re: [translations] Changes section in stable

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

Re: check_translation crashes

Le 08/03/2020 à 18:33, Jonas Hahnfeld a écrit : Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles Malahieude: It might be useful in other places as well, I don't know. What do you mean? I hope I got most other scripts covered. Please let me know if I missed other as well. It's

Re: Doc: organize changes.tely

Le 08/03/2020 à 18:34, pkx1...@posteo.net a écrit : The sectioning was done based on (sort of) how the NR is organized and I thought it would be more useful for users to search for something based on its type of enhancement/change than just in the order the changes were added. And it was a

Re: check_translation crashes

Le 08/03/2020 à 18:16, Jonas Hahnfeld a écrit : Am Samstag, den 07.03.2020, 11:27 +0100 schrieb Jean-Charles Malahieude: Hi all, As I'm done with the French translations for 2.20, I'd like to now take care of 2.21 but… my workflow is now broken and I'm not able to diagnose what's wrong

Doc: organize changes.tely

Hi all, Purging the French version of changes.tely, came to my mind it might be wise to avoid moving around and re-organize items like James did in late 2017 when preparing for a new major release (and translators afterwards) and have it structured on the fly. This was the first time for

check_translation crashes

Hi all, As I'm done with the French translations for 2.20, I'd like to now take care of 2.21 but… my workflow is now broken and I'm not able to diagnose what's wrong. The only change in the body of check_translation.py since 2009 has been introduced with issue 5646. A "python --version" gives

Re: Getting download sizes right: proof of concept

Le 26/02/2020 à 02:18, David Kastrup a écrit : Anybody want to see what it takes to get this across the finishing line? Just a nitpick: the sizes are in Documentation/web/manuals.itexi. I'll have a look this afternoon. Cheers, -- Jean-Charles

Re: testing out Docker CI scripts?

Le 23/02/2020 à 16:38, David Kastrup a écrit : Why wouldn't either of you be using the CPU_COUNT= ... environment variable for letting lilypond-book run parallel jobs of lilypond ? I forgot to mention that I've a Traduc (translation)]$ cat local.make CPU_COUNT = 4

Re: testing out Docker CI scripts?

Le 23/02/2020 à 15:56, Han-Wen Nienhuys a écrit : On Sun, Feb 23, 2020 at 11:44 AM Han-Wen Nienhuys wrote: and initially it is working as expected (4 cpus.) 11:12:40 3.23 Making Documentation/out-www/music-glossary.pdf < texi 11:12:41 3.30 Making Documentation/out-www/notation.pdf < texi

Re: [translations] 2.20 and 2.21 release plans

Le 17/02/2020 à 13:25, David Kastrup a écrit : Ok, I think 2.20 is basically done and we should push it out by the end of this week. This leaves a few days for the translation team to catch up with the current state. In particular HINT HINT HINT it gives the opportunity to native speakers of

Re: lilypond.org now serving HTTPS

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

Re: lilypond-2.19.84

Le 06/02/2020 à 20:10, Benkő Pál a écrit : the News section at lilypond.org dates 2.19.84 to 2019. can I (or anyone else) push a fix to staging? I would prefer Phil or David to take care of this silly calendar not wanting to go ahead… Cheers, -- Jean-Charles

Re: Documentation suggestions.

Le 05/02/2020 à 23:30, Michael Käppler a écrit : Dear Peter, it would be nice if you could register yourself at Rietveld. If you already have a Google account it should be straightforward, I think. Please see the updated issue at: https://codereview.appspot.com/579280043/ You don't need a

Re: [translations] Remaining sprint for the release of version 2.20

Le 06/02/2020 à 00:44, David Kastrup a écrit : Whatever else may be on the plate, the immediate problem to be put behind us right now is the release of 2.20. I put specifically the translation team and Werner into Cc. The translation team should check what changes of the recent release of

lilypond-2.19.84

Hi, Please find a new tarball for LilyPond at http://lilypond.org/download/source/v2.19/lilypond-2.19.84.tar.gz Cheers, -- Jean-Charles Malahieude

Re: stable/2.20 branch does not complete "make doc"

Le 30/01/2020 à 19:46, David Kastrup a écrit : Oops. dak@lola:/usr/local/tmp/lilypond$ git checkout origin error: The following untracked working tree files would be overwritten by checkout: Documentation/snippets/non-traditional.snippet-list Please move or remove them before you

Re: Build problem with fonts

Le 08/12/2019 à 18:12, Werner LEMBERG a écrit : Please try again with strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf so that we can see the strace messages from `t1asm` also. Note that you will get at least two files called `mf2pt1.strace.X`, where `X` is a process ID. Four

Re: Build problem with fonts

Le 08/12/2019 à 17:10, Werner LEMBERG a écrit : Strange indeed. Can you temporarily replace `mf2pt1` with a script that calls `strace`? Something like strace mf2pt1 ... &> ~/mf2pt1.strace.log You could then investigate in more detail which files `mf2pt1` tries to open and/or execute.

Re: Build problem with fonts

Le 08/12/2019 à 16:51, Werner LEMBERG a écrit : Can you execute t1asm? t1asm --help It works either in $HOME or in my compiling folders. Is it in your path that you use for compiling lilypond? which t1asm /usr/bin/t1asm so I don't see any reason why, just at once, it failed at

Build problem with fonts

Hi all, For about two weeks now, I'm unable to build and then merge translation with stable, even after a fresh clone. I cannot believe it has something to do with an upgrade from Fedora 30 to 31. Tail of the log : --8<-- cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe Copyright

Re: build problem

Le 26/07/2019 à 09:44, Federico Bruni a écrit : Jean-Charles, version 1.0.3 is now available in Fedora 30 repositories. And version 1.1.0 is in rawhide. As I've cloned the repository and built it without any problem, everything is fine. Cheers, Jean-Charles

Re: build problem

Le 30/06/2019 à 11:10, Knut Petersen a écrit : Build it yourself. Building and installing extractpdfmark is an easy an fast task. Cloning the repository, building, testing and installing of extractpdfmark takes less than 20 seconds here: This, as intended, works like a charm, but I was

Re: build problem

Le 30/06/2019 à 02:51, Masamichi Hosoda a écrit : In Fedora 30, I suggest to use extractpdfmark from package, rather than self-built extractpdfmark. https://apps.fedoraproject.org/packages/extractpdfmark If I understand correctly, Fedora 30 has popler-0.73.0 package that has libpoppler.so.84.

build problem

Hello, Since I can't get a successful doc-build on my Fedora 30 box, I'm unable to check doc-changes and merge translation into stable. It's the same with extractpdfmark 1.0.2 1.0.3 and 1.1.0 log spits: extractpdfmark -o ./out-www/collated-files.pdfmark ./out-www/collated-files.tmp.pdf

Re: Google Season of Docs

Le 05/04/2019 à 20:46, Werner LEMBERG a écrit : Would this be of interest for LilyPond? This might help us going forward and profit from the evolution of texinfo, as well as recover the use of lilypond-doc.po that vanished with GDP. Cheers, Jean-Charles

Release plan

In order to make available the various updates to translations of our documentation (thanks to Federico, Francisco, Walter and Tomohiro Tatejima) would it be possible to release a 2.19.82? Cheers, Jean-Charles ___ lilypond-devel mailing list

core dump

Hi all, Trying to compile one of Nicolas Sceaux' score, I get a core dump. Strange thing is the message, depending on the binary: with the downloaded and installed 2.19.80, it says lilypond:

lilypond-2.19.80

Hi, Please find a new tarball for LilyPond at http://download.linuxaudio.org/lilypond/source/v2.19/lilypond-2.19.80.tar.gz Cheers, Jean-Charles Malahieude ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo

Changes.tely

Hi James, I didn't review your patch, but Documentation/changes-splittexi.log contains WARNING: Unable to find node 'Isolated durations in music now stand for unpitched notes' in book notation. Seems to be a wrong command in changes.tely -- lines 335 @noindent with multiple exceptions

Re: make test fails → texi2html (?) error

Le 06/10/2017 à 16:27, Malte Meyn a écrit : Hi list, I tried to compile the regression tests (make test) but this failed with the following message in input/regression/collated-files.texilog.log: Undefined subroutine ::get_index called at

Absence

Hi all, Sorry not to be active for the past two weeks, but a family "disaster" will keep me away from any activity for this week as well. I'll let David, Federico or Francisco do the merging between stable/2.20 and translation until Monday 9th. I might just be able to read some mails on my

Re: translation branch and stable/2.20 branch

Le 08/08/2017 à 16:48, Masamichi Hosoda a écrit : 2.19.65 has been released, it seems that it does not contain some recent translations. [...] Which branch should the translators translate? e.g. translate the English document in the master branch, commit to the translation branch, etc.

Re: Any objections to branching off a stable branch for 2.20?

Le 19/07/2017 à 14:48, David Kastrup a écrit : Federico Bruni writes: Il giorno lun 17 lug 2017 alle 19:14, David Kastrup ha scritto: Other things up for cherry-picking are documentation changes and their translations. Since translations usually are done in "bulk", it would make sense to

Re: help with bash script to translate @ref{} items in translated manuals

Le 21/04/2017 à 17:59, Federico Bruni a écrit : Il giorno ven 21 apr 2017 alle 15:54, k...@aspodata.se ha scritto: You already have such an replacement file in Documentation/po/it.po: $ fgrep -C2 'Different editions from one source' Documentation/po/it.po #. @node in

Re: [LilyIssues-auto] [testlilyissues:issues] #4966 the font name is Emmentaler, while Feta and Parmesan are two subsets of glyphs

Le 12/03/2017 à 11:37, Federico Bruni a écrit : Il giorno dom 12 mar 2017 alle 11:10, Jean-Charles Malahieude No, the two typos are still there... Sorry, take a look at commit 1e5c6b0f54079eb3285dcc4c7e53f17d8bb03933 Doc: typos and spurious seealso Seems like documentation in not rebuilt

Re: [LilyIssues-auto] [testlilyissues:issues] #4966 the font name is Emmentaler, while Feta and Parmesan are two subsets of glyphs

Le 12/03/2017 à 10:50, David Kastrup a écrit : Auto mailings of changes to Lily Issues writes: James, I think that you can mark this issue as fixed and I'll create a new issue for the fourth item in the above list. I have only two comments about

lilypond-2.19.54

Hi, Please find a new tarball for LilyPond at http://download.linuxaudio.org/lilypond/source/v2.19/lilypond-2.19.54.tar.gz Cheers, Jean-Charles Malahieude ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman

Re: New LilyPond website

Le 03/12/2016 à 22:28, Graham Percival a écrit : On Fri, Dec 02, 2016 at 07:50:50PM +0100, Jean-Charles Malahieude wrote: I've already given it a try, but get stopped by some errors I don't know how to resolve (I've no knowledge about perl). Three patches are available for anybody willing

Re: New LilyPond website

Le 02/12/2016 à 02:10, Paul a écrit : Hi Carl, On 12/01/2016 12:44 PM, Carl Sorensen wrote: One thing that is note mentioned in your quote is that texinfo separates semantics from appearance. It is this precise separation that allows one to make big but consistent changes in the appearance of

Re: Stepping down and moving on

Le 09/11/2016 à 18:09, David Kastrup a écrit : Hi folks and team, while I haven't really occupied an official function in LilyPond development, it's hard to deny that I have effectively functioned as acting chief architect and vetter (with a rather mottled performance). I have accepted a

Re: Patchy email

Le 28/09/2016 à 13:23, James a écrit : Now if only Jean-Charles, Graham et al, could script checking reg test diffs and finding obscure make errors in all the .log files we generate ;) I'm not good at all with scripting, but could try to track down the logs. What would you like me to do in

Re: Mail to tranlati...@lilynet.net failing

Le 27/08/2016 à 10:05, Walter Garcia-Fontes a écrit : Mail to lilynet.net is failing with the following error: Delivery to the following recipient failed permanently: translati...@lilynet.net Technical details of permanent failure: DNS Error: 21251920 DNS type 'mx' lookup of lilynet.net

Re: State of staging branch?

Le 08/05/2016 à 16:30, David Kastrup a écrit : "Phil Holmes" writes: Compile was fine and staging pushed to master. I guess James's patchy machine is having connectivity problems or similar. Ok... Just for interest: your system is 64bit? Mine is 32bit and still at

Re: hyphen syntax

Le 14/02/2016 20:41, Dan Eble a écrit : Are there technical limitations that require typing a double hyphen to hyphenate lyrics? Why not just one? Technically, I don't know. But, in terms of coherence, I would leave it as it is: one hyphen is treated as one syllable, just like one

Re: Musicians prefer LilyPond scores, study finds

Le 17/12/2015 17:53, Francisco Vila a écrit : Hello, I just gained my PhD. My humble thesis tells the design and results of an experiment with a number of musicians, comparing lilypond scores with the originals which those scores were copied from. Congratulations! Now I will try to

Re: I seem to have broken staging

Le 17/11/2015 22:37, David Kastrup a écrit : Thomas Morley writes: Hm, before I pushed this, I had gotten a merge conflict while rebasing. Was in "/Documentation/notation/fretted-strings.itely", iirc. Resolved it manually. Though, I didn't even touch the french or

lilypon.org down

LP.org is down here in France since yesterday afternoon. Are we the only one? Cheers, Jean-Charles ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: lilypon.org down

Le 31/10/2015 14:03, bobr...@centrum.is a écrit : According to: http://www.downforeveryoneorjustme.com/lilypond.org It's down. -David From: "Jean-Charles Malahieude" LP.org is down here in France since yesterday afternoon. Are we the only one? But download.linuxaudio.or

Re: lilypond.org - file storage

Le 30/08/2015 17:45, Graham Percival a écrit : On Sun, Aug 30, 2015 at 01:15:48PM +0100, Phil Holmes wrote: We also have source files back to 0.0 and 1.0. I assume we could never recreate these from Git, but are we ever going to need to? It certainly seems pointless keeping lots of source

lilypond-2.19.26

Hi, Please find a new tarball for LilyPond at http://download.linuxaudio.org/lilypond/source/v2.19/lilypond-2.19.26.tar.gz Cheers, Jean-Charles Malahieude ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman

Re: Remove old News entry from home page

Le 19/07/2015 08:25, Federico Bruni a écrit : […] 2. We still depend on texi2html and the help request by Jean-Charles, who tried moving to texi2any, not surprisingly was ignored: http://lists.gnu.org/archive/html/lilypond-devel/2015-05/msg00032.html [Werner] The `non surprisingly' is

Re: issue 1557: Migration from texi2html to texi2any

Le 02/05/2015 20:18, Jean-Charles Malahieude a écrit : What I've tried so far is: 4- replace any occurrence of @documentlanguage utf-8 by @documentlanguage UTF-8 and add it where needed Oops! should have read before sending: 4- @documentencoding UTF-8 Could anybody help? Cheers, Jean

issue 1557: Migration from texi2html to texi2any

Hi all! Texinfo evolves, and so does texi2any. What I've tried so far is: 1- build and install a new 5.9.90 texinfo 2- uninstall texi2html 3- ln -s /usr/bin/texi2any ~/ME/bin/texi2html 4- replace any occurrence of @documentlanguage utf-8 by @documentlanguage UTF-8 and add it where needed

  1   2   3   4   >