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

2017-04-21 Thread Andrew Bernard
Hi Federico, I believe you are trying to automate a set of translations, correct? If so, here's a way to do it in perl that avoids all the shell convolutions. I assume you do know perl. If not, always worth knowing for this sort of quick work. Just add the translations to the hash table in the

Re: LilyPond Slack channel

2017-04-21 Thread Jeffery Shivers
On Fri, Apr 21, 2017 at 10:24 PM Jeffery Shivers wrote: > > So I'd like to know general thoughts about the use of such a system in > the first place, for GSoC, but also if people might see a use for it > outside of the scope of LilyPond. Oops - I mean *outside of the

LilyPond Slack channel

2017-04-21 Thread Jeffery Shivers
Hi everyone, I thought it might be useful to create a Slack channel for LilyPond, particularly with the advent of another Google Summer of Code term. Most GSoC orgs encourage some sort of IRC or other chat protocol for students / mentors / admins to interact, but of course the downside is that

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

2017-04-21 Thread Flaming Hakama by Elaine
> From: Federico Bruni > To: Dev > Date: Thu, 20 Apr 2017 08:20:26 +0200 > Subject: help with bash script to translate @ref{} items in translated > manuals > Hi all > > I recently realized that @ref{} links should be translated otherwise PDF > links

PATCHES - Countdown for April 21st

2017-04-21 Thread James
Hello, Here is the current patch countdown list. The next countdown will be on April 24th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Push: No patches to Push at this time. Countdown 5122 Fix not scaling

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

2017-04-21 Thread Jean-Charles Malahieude
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: help with bash script to translate @ref{} items in translated manuals

2017-04-21 Thread Federico Bruni
Il giorno ven 21 apr 2017 alle 15:54, k...@aspodata.se ha scritto: It is expecting something from stdin. You didn't tell us where the replacement data comes from, so I guessed you run your script as cat repl.txt | your_script Actually in my first attempt I thought I'd have entered the

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

2017-04-21 Thread Federico Bruni
Il giorno ven 21 apr 2017 alle 15:54, k...@aspodata.se ha scritto: Federico Bruni: Il giorno ven 21 apr 2017 alle 7:08, Federico Bruni ha scritto: > I guess I'll have to revert to my almost manual replacement I've used > so far. Or I may try a different approach

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

2017-04-21 Thread karl
Federico Bruni: > Il giorno ven 21 apr 2017 alle 7:08, Federico Bruni > ha scritto: > > I guess I'll have to revert to my almost manual replacement I've used > > so far. > > Or I may try a different approach and script a replacement from a file > like: > > @ref{Different

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

2017-04-21 Thread karl
Frederico Bruni: > Il giorno gio 20 apr 2017 alle 11:22, k...@aspodata.se ha scritto: > > Frederico Bruni: > > ... > >> Enter Documentation/it/notation and run this: > >> > >> #!/bin/bash > >> LIST="$(grep -oh -e @ref{.*} *.itely | sort -u)" > >> for i in $LIST; do > >> echo $i > >> #