Re: fixing website translations
Il giorno lun, 22/08/2011 alle 13.53 +0200, Federico Bruni ha scritto:
Il giorno lun, 22/08/2011 alle 00.57 -0700, Graham Percival ha scritto:
There is NO SUCH @node called {Text editor support}. You have
named that @node LilyPond e gli editor di testo. So fix your
Documentation/it/web/introduction.itexi
Do the same for the other two lines as well.
Ok, thanks. Now it's fixed.
See patch attached: it should be applied to the lilypond-translation
branch.
It contains other fixes and updates. Also, I've decided to drop the
translation of news-front (I had translated just 3 news so far..), because I
don't think it's worth and I prefer being sure that italian users can
see updated news (even if in english).
Francisco,
I think you forgot to apply this patch, right?
I can see from git log that you are back from holidays :)
Thanks,
Federico
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
2011/8/29 Federico Bruni fedel...@gmail.com:
Il giorno lun, 22/08/2011 alle 13.53 +0200, Federico Bruni ha scritto:
Il giorno lun, 22/08/2011 alle 00.57 -0700, Graham Percival ha scritto:
There is NO SUCH @node called {Text editor support}. You have
named that @node LilyPond e gli editor di testo. So fix your
Documentation/it/web/introduction.itexi
Do the same for the other two lines as well.
Ok, thanks. Now it's fixed.
See patch attached: it should be applied to the lilypond-translation
branch.
It contains other fixes and updates. Also, I've decided to drop the
translation of news-front (I had translated just 3 news so far..), because I
don't think it's worth and I prefer being sure that italian users can
see updated news (even if in english).
Francisco,
I think you forgot to apply this patch, right?
I can see from git log that you are back from holidays :)
Thanks,
Federico
I'll take a look at it. Thank you
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
2011/8/29 Francisco Vila paconet@gmail.com: I'll take a look at it. Thank you Done. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
On Mon, Aug 22, 2011 at 12:57:41AM +0200, Federico Bruni wrote:
Il giorno ven, 12/08/2011 alle 09.07 -0700, Graham Percival ha scritto:
WARNING: Unable to find node 'Text editor support' in book usage.
WARNING: Unable to find node 'Troubleshooting' in book usage.
WARNING: Unable to find node 'Why does the syntax change?' in book
usage.
Given that the documentation is different from the web site, I'm
not convinced.
AFAIK, in the website there's not any link to any node in Usage.
So I can't understand why 'make website' prints this warning.
gperciva@bluespark:~/src/lilypond/Documentation/it$ git grep Text
editor support
usage/external.itely:@translationof Text editor support
web/introduction.itexi:@rprogram{Text editor support}.
inside Documentation/it/external.itely, I see this:
@node LilyPond e gli editor di testo
@section LilyPond e gli editor di testo
@translationof Text editor support
There is NO SUCH @node called {Text editor support}. You have
named that @node LilyPond e gli editor di testo. So fix your
Documentation/it/web/introduction.itexi
Do the same for the other two lines as well.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
Il giorno lun, 22/08/2011 alle 00.57 -0700, Graham Percival ha scritto:
There is NO SUCH @node called {Text editor support}. You have
named that @node LilyPond e gli editor di testo. So fix your
Documentation/it/web/introduction.itexi
Do the same for the other two lines as well.
Ok, thanks. Now it's fixed.
See patch attached: it should be applied to the lilypond-translation
branch.
It contains other fixes and updates. Also, I've decided to drop the
translation of news-front (I had translated just 3 news so far..), because I
don't think it's worth and I prefer being sure that italian users can
see updated news (even if in english).
Cheers,
Federico
From beb014d984d0fe494d50ebf4ea344a72b3994019 Mon Sep 17 00:00:00 2001
From: Federico Bruni fedel...@gmail.com
Date: Mon, 22 Aug 2011 12:05:24 +0200
Subject: [PATCH] Web-it: update italian translation, add helpus and
generating-output macros and remove news-front.
---
Documentation/it/included/generating-output.itexi | 226 +
Documentation/it/included/helpus.itexi| 145 +
Documentation/it/web.texi | 13 +-
Documentation/it/web/community.itexi | 88 +++--
Documentation/it/web/download.itexi | 22 ++-
Documentation/it/web/introduction.itexi | 42 +++--
Documentation/it/web/manuals.itexi| 111 ++-
Documentation/it/web/news-front.itexi | 70 ---
8 files changed, 547 insertions(+), 170 deletions(-)
create mode 100644 Documentation/it/included/generating-output.itexi
create mode 100644 Documentation/it/included/helpus.itexi
delete mode 100644 Documentation/it/web/news-front.itexi
diff --git a/Documentation/it/included/generating-output.itexi b/Documentation/it/included/generating-output.itexi
new file mode 100644
index 000..45d34ee
--- /dev/null
+++ b/Documentation/it/included/generating-output.itexi
@@ -0,0 +1,226 @@
+@c -*- coding: utf-8; mode: texinfo; documentlanguage: it -*-
+@c This file is part of web/download.itexi and
+@c learning/tutorial.itely
+@ignore
+Translation of GIT committish: 8f02aa6516b3cfe16b2c145142ea652cbc3b8970
+
+When revising a translation, copy the HEAD committish of the
+version that you are working on. For details, see the Contributors'
+Guide, node Updating translation committishes..
+@end ignore
+
+@c This is about compiling a lilypond file
+@c (Learning 1 Tutorial), **not** compiling the
+@c source code.
+
+@macro lilypadOSX
+@warning{Queste istruzioni presumono che tu stia usando il programma
+LilyPond. Se stai usando uno dei programmi descritti in
+@rweb{Editing facilitato}, in caso di problemi consulta la documentazione
+di quei programmi.}
+
+
+@subsubheading Passo 1. Crea il tuo file @file{.ly}
+
+Clicca due volte su @command{LilyPond.app}, si aprirà un file di esempio.
+
+@sourceimage{Learning_Macos_welcome,,,}
+
+Dai menu in cima a sinistra dello schermo seleziona
+@w{@code{File Save}}.
+
+@sourceimage{Learning_Macos_Save_menu,,,}
+
+Scegli un nome per il tuo file, ad esempio @file{test.ly}.
+
+@sourceimage{Learning_Macos_Save_file_with_name,,,}
+
+
+@subsubheading Passo 2. Compila (con LilyPad)
+
+Dagli stessi menu seleziona
+@w{@code{Compile Typeset}}.
+
+@sourceimage{Learning_Macos_Typeset_menu,,,}
+
+Si aprirà una nuova finestra che mostra i messaggi di log della compilazione
+del file che hai appena salvato.
+
+@sourceimage{Learning_Macos_Compiling_log,,,}
+
+
+@subsubheading Passo 3. Visualizza l'output
+
+Quando la compilazione è finita, un file PDF con lo stesso nome del file
+originale viene creato e automaticamente aperto nel visualizzatore
+PDF predefinito, che lo mostrerà sullo schermo.
+
+@sourceimage{Learning_Macos_pdf_output,,,}
+
+
+@subsubheading Altri comandi
+
+Per creare nuovi file per LilyPond, comincia col selezionare
+@w{@code{File New}}
+
+@sourceimage{Learning_Macos_New_menu,,,}
+
+oppure @w{@code{File Open}} per aprire e modificare file esistenti che
+hai salvato precedentemente.
+
+@sourceimage{Learning_Macos_Open_menu,,,}
+
+Devi salvare qualsiasi nuova modifica fatta al file prima di cliccare
+@w{@code{Compile Typeset}} e se il file PDF non compare controlla se
+ci sono degli errori nella finestra dei messaggi di log.
+
+Se non stai usando il visualizzatore d'anteprima PDF incluso nel sistema
+operativo del Mac e un file PDF generato da una compilazione precedente
+è aperto, qualsiasi compilazione successiva potrebbe non riuscire a
+generare un PDF aggiornato finché non chiudi l'originale.
+
+
+
+@end macro
+
+
+@macro lilypadWindows
+@warning{Queste istruzioni presumono che tu stia usando l'editor LilyPad
+incluso nel programma. Se stai usando uno dei programmi descritti in
+@rweb{Editing facilitato}, in caso di problemi nel compilare un file consulta
+la documentazione di quei programmi.}
+
+
+@subsubheading Passo 1. Crea il tuo file @file{.ly}
+
+Clicca due volte sull'icona di LilyPond
Re: fixing website translations
Il giorno ven, 12/08/2011 alle 09.07 -0700, Graham Percival ha scritto: On Fri, Aug 12, 2011 at 05:27:53PM +0200, Francisco Vila wrote: 2011/8/12 Federico Bruni fedel...@gmail.com: Il giorno ven, 12/08/2011 alle 16.49 +0200, Francisco Vila ha scritto: Processing web site: [it] WARNING: Unable to find node 'Text editor support' in book usage. WARNING: Unable to find node 'Troubleshooting' in book usage. WARNING: Unable to find node 'Why does the syntax change?' in book usage. I gave a quick look at 2.14.2 doc and couldn't find any broken link (from Usage or from Learning Manual). Except for a broken link in the appendix A of LM; but it is not related to the warning above. Given that the documentation is different from the web site, I'm not convinced. AFAIK, in the website there's not any link to any node in Usage. So I can't understand why 'make website' prints this warning. Apparently, the 'Warning: unable to find x in book y' messages do not lead necessarily to broken links. IMO they are a side effect of old, unused code. FFS...! other languages have managed to fix these. For that matter, you don't even need to read the language to fix these problems! - we no longer have text editor support in Usage. What has that node been renamed to? Go update the name. - ditto for the other two. Are you sure? git grep says the opposite. What I'm missing? If you can't remember anything like this, then go look in the archives for the other 4 or 5 times I've complained about similar problems. Translators fixed those ones fairly quickly; either ask them how they did it, or look at the git history to find out how. Mh, I'll try but I think it won't be easy. I haven't found any specific discussion so far. It may be a stupid error, such a missing brace } ? There's any script which can help in finding such errors? For example: http://lists.gnu.org/archive/html/lilypond-devel/2011-01/msg00166.html but the log was informative in that case... ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
2011/7/30 Graham Percival gra...@percival-music.ca: I've been seeing these warnings for months: Processing web site: [cs] WARNING: Unable to find node 'Řešení potíží' in book usage. WARNING: Unable to find node 'Proč se mění skladba?' in book usage. Processing web site: [de] Processing web site: [es] Processing web site: [fr] Processing web site: [hu] Processing web site: [it] WARNING: Unable to find node 'Text editor support' in book usage. WARNING: Unable to find node 'Troubleshooting' in book usage. WARNING: Unable to find node 'Why does the syntax change?' in book usage. could somebody fix them? This message seems to have been largely ignored. I often see similar warnings on make doc, but not that few, rather hundredths of them. As the excerpt you post refers to [cs] and [it], I forward to Pavel and Federico. Thanks, -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
Il giorno ven, 12/08/2011 alle 16.49 +0200, Francisco Vila ha scritto: Processing web site: [it] WARNING: Unable to find node 'Text editor support' in book usage. WARNING: Unable to find node 'Troubleshooting' in book usage. WARNING: Unable to find node 'Why does the syntax change?' in book usage. could somebody fix them? This message seems to have been largely ignored. I often see similar warnings on make doc, but not that few, rather hundredths of them. As the excerpt you post refers to [cs] and [it], I forward to Pavel and Federico. I gave a quick look at 2.14.2 doc and couldn't find any broken link (from Usage or from Learning Manual). Except for a broken link in the appendix A of LM; but it is not related to the warning above. Well, I'm not good at finding the source of problems. I'm going in holidays, I won't be able to check it before the end of August. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
2011/8/12 Federico Bruni fedel...@gmail.com: Il giorno ven, 12/08/2011 alle 16.49 +0200, Francisco Vila ha scritto: Processing web site: [it] WARNING: Unable to find node 'Text editor support' in book usage. WARNING: Unable to find node 'Troubleshooting' in book usage. WARNING: Unable to find node 'Why does the syntax change?' in book usage. could somebody fix them? This message seems to have been largely ignored. I often see similar warnings on make doc, but not that few, rather hundredths of them. As the excerpt you post refers to [cs] and [it], I forward to Pavel and Federico. I gave a quick look at 2.14.2 doc and couldn't find any broken link (from Usage or from Learning Manual). Except for a broken link in the appendix A of LM; but it is not related to the warning above. Apparently, the 'Warning: unable to find x in book y' messages do not lead necessarily to broken links. IMO they are a side effect of old, unused code. Well, I'm not good at finding the source of problems. I'm going in holidays, I won't be able to check it before the end of August. Same for me. I still have 2/3 days available. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: fixing website translations
On Fri, Aug 12, 2011 at 05:27:53PM +0200, Francisco Vila wrote: 2011/8/12 Federico Bruni fedel...@gmail.com: Il giorno ven, 12/08/2011 alle 16.49 +0200, Francisco Vila ha scritto: Processing web site: [it] WARNING: Unable to find node 'Text editor support' in book usage. WARNING: Unable to find node 'Troubleshooting' in book usage. WARNING: Unable to find node 'Why does the syntax change?' in book usage. I gave a quick look at 2.14.2 doc and couldn't find any broken link (from Usage or from Learning Manual). Except for a broken link in the appendix A of LM; but it is not related to the warning above. Given that the documentation is different from the web site, I'm not convinced. Apparently, the 'Warning: unable to find x in book y' messages do not lead necessarily to broken links. IMO they are a side effect of old, unused code. FFS...! other languages have managed to fix these. For that matter, you don't even need to read the language to fix these problems! - we no longer have text editor support in Usage. What has that node been renamed to? Go update the name. - ditto for the other two. If you can't remember anything like this, then go look in the archives for the other 4 or 5 times I've complained about similar problems. Translators fixed those ones fairly quickly; either ask them how they did it, or look at the git history to find out how. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
