gnucash-docs maint: Bug 796820 - References to "Gnome Bugzilla" should be changed to "GnuCash Bugzilla"

Geert Janssens gjanssens at code.gnucash.org
Fri Sep 28 11:24:09 EDT 2018


Updated	 via  https://github.com/Gnucash/gnucash-docs/commit/a1977130 (commit)
	from  https://github.com/Gnucash/gnucash-docs/commit/effc483b (commit)



commit a1977130a65c39228f908b45ca456690eed6ec4c
Author: Geert Janssens <geert at kobaltwit.be>
Date:   Fri Sep 28 17:23:54 2018 +0200

    Bug 796820 - References to "Gnome Bugzilla" should be changed to "GnuCash Bugzilla"

diff --git a/guide/C/appendixb.xml b/guide/C/appendixb.xml
index d13f60d..421b3cd 100644
--- a/guide/C/appendixb.xml
+++ b/guide/C/appendixb.xml
@@ -75,7 +75,7 @@
 
       <sect2 id="appendixb_general_newFeatures">
         <title>Q: I really want feature XYZ but <application>&app;</application> doesn’t have it. How do I get it added?</title>
-        <para>A: Ask nicely. :-) You can file an enhancement request at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to describe your proposed enhancement as verbosely as possible. The trick here is to learn how to give the best information to the programmers about what your proposed new feature should do. If you want to speed up development significantly, consider donating some money as described on <application>&app;</application>Development.</para>
+        <para>A: Ask nicely. :-) You can file an enhancement request at <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to describe your proposed enhancement as verbosely as possible. The trick here is to learn how to give the best information to the programmers about what your proposed new feature should do. If you want to speed up development significantly, consider donating some money as described on <application>&app;</application>Development.</para>
       </sect2>
 
       <sect2 id="appendixb_software_web">
@@ -95,8 +95,8 @@
 
       <sect2 id="appendixb_software_bugs">
         <title>Q: I think I found a bug. How do I report it?</title>
-        <para>A: First of all, try to verify that it is indeed a bug and that it has not been reported before. Search the mail list archives (see FAQ above). Then search the <ulink url="http://bugzilla.gnome.org">Gnome Bugzilla</ulink> database.</para>
-        <para>If you feel you have indeed found a bug, you can then report it at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to report your bug as verbosely as possible. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can’t make the programmer see your bug, it won’t get fixed!</para>
+        <para>A: First of all, try to verify that it is indeed a bug and that it has not been reported before. Search the mail list archives (see FAQ above). Then search the <ulink url="http://bugs.gnucash.org">&app; Bugzilla</ulink> database.</para>
+        <para>If you feel you have indeed found a bug, you can then report it at <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to report your bug as verbosely as possible. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can’t make the programmer see your bug, it won’t get fixed!</para>
       </sect2>
 
     </sect1>
diff --git a/guide/C/gnucash-guide.xml b/guide/C/gnucash-guide.xml
index 1eb3d46..f83d35e 100644
--- a/guide/C/gnucash-guide.xml
+++ b/guide/C/gnucash-guide.xml
@@ -395,8 +395,8 @@
         this manual, follow the instructions at the
         <ulink url="https://wiki.gnucash.org/wiki/Bugzilla"
           >Bugzilla page of the GnuCash wiki</ulink> and use the
-        <ulink url="https://bugzilla.gnome.org/browse.cgi?product=GnuCash"
-          >GNOME Bug Tracking System</ulink>. There select the component
+        <ulink url="https://bugs.gnucash.org/browse.cgi?product=GnuCash"
+          >&app; Bug Tracking System</ulink>. There select the component
         <emphasis>Documentation</emphasis><!-- Translators uncomment the next line: -->
         <!--  or <emphasis>Translations</emphasis> -->.
       </para>
diff --git a/guide/de/appendixb.xml b/guide/de/appendixb.xml
index ba039f8..c322a36 100644
--- a/guide/de/appendixb.xml
+++ b/guide/de/appendixb.xml
@@ -77,7 +77,7 @@
 
       <sect2 id="appendixb_general_newFeatures">
         <title>Q: I really want feature XYZ but <application>&app;</application> doesn’t have it. How do I get it added?</title>
-        <para>A: Ask nicely. :-) You can file an enhancement request at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to describe your proposed enhancement as verbosely as possible. The trick here is to learn how to give the best information to the programmers about what your proposed new feature should do. If you want to speed up development significantly, consider donating some money as described on <application>&app;</application>Development.</para>
+        <para>A: Ask nicely. :-) You can file an enhancement request at <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to describe your proposed enhancement as verbosely as possible. The trick here is to learn how to give the best information to the programmers about what your proposed new feature should do. If you want to speed up development significantly, consider donating some money as described on <application>&app;</application>Development.</para>
       </sect2>
 
       <sect2 id="appendixb_software_web">
@@ -97,8 +97,8 @@
 
       <sect2 id="appendixb_software_bugs">
         <title>Q: I think I found a bug. How do I report it?</title>
-        <para>A: First of all, try to verify that it is indeed a bug and that it has not been reported before. Search the mail list archives (see FAQ above). Then search the <ulink url="http://bugzilla.gnome.org">Gnome Bugzilla</ulink> database.</para>
-        <para>If you feel you have indeed found a bug, you can then report it at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to report your bug as verbosely as possible. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can’t make the programmer see your bug, it won’t get fixed!</para>
+        <para>A: First of all, try to verify that it is indeed a bug and that it has not been reported before. Search the mail list archives (see FAQ above). Then search the <ulink url="http://bugs.gnucash.org">&app; Bugzilla</ulink> database.</para>
+        <para>If you feel you have indeed found a bug, you can then report it at <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to report your bug as verbosely as possible. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can’t make the programmer see your bug, it won’t get fixed!</para>
       </sect2>
 
     </sect1>
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index f33bf4f..e8eb62f 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -405,8 +405,8 @@
         Verbesserungsvorschlag einzureichen, folgen Sie den Anweisungen auf der
         <ulink url="https://wiki.gnucash.org/wiki/De/Feedback"
           >Feedbackseite des GnuCash-Wikis</ulink> und verwenden das
-        <ulink url="https://bugzilla.gnome.org/browse.cgi?product=GnuCash"
-          >GNOME Bug Tracking System</ulink>. Dort wählen Sie, je nach Ursache, die Komponente <emphasis>Documentation</emphasis> oder <emphasis>Translations</emphasis>.
+        <ulink url="https://bugs.gnucash.org/browse.cgi?product=GnuCash"
+          >&app; Bug Tracking System</ulink>. Dort wählen Sie, je nach Ursache, die Komponente <emphasis>Documentation</emphasis> oder <emphasis>Translations</emphasis>.
       </para>
 <!-- Translators may also add here a feedback address for translations -->
   </legalnotice>
diff --git a/guide/it/gnucash-guide.xml b/guide/it/gnucash-guide.xml
index f1fbb11..e97d6a4 100644
--- a/guide/it/gnucash-guide.xml
+++ b/guide/it/gnucash-guide.xml
@@ -344,7 +344,7 @@
   <releaseinfo>Questa guida contiene un esempio pratico di utilizzo di &app; e descrive i concetti su cui &app; si basa.</releaseinfo>
   <legalnotice>
     <title>Feedback</title>
-      <para>Per segnalare dei bug o proporre dei suggerimenti riguardanti questo programma o questo manuale, seguire le indicazioni fornite in <ulink url="http://bugzilla.gnome.org">GNOME Bug Tracking System</ulink>.</para>
+      <para>Per segnalare dei bug o proporre dei suggerimenti riguardanti questo programma o questo manuale, seguire le indicazioni fornite in <ulink url="http://bugs.gnucash.org">&app; Bug Tracking System</ulink>.</para>
 <!-- Translators may also add here a feedback address for translations -->
   </legalnotice>
 
@@ -12860,7 +12860,7 @@ work on earlier versions, too.</para>
 
       <sect2 id="appendixb_general_newFeatures">
         <title>D: Vorrei usare la funzione XYZ ma <application>&app;</application> non ce l’ha. Come posso fare?</title>
-        <para>R: Chiedi gentilmente. :-) Puoi presentare una richiesta qui <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=gnucash"/>. Ricorda di descrivere il più dettagliatamente possibile la caratteristica che vorresti vedere implementata. Il trucco sta tutto nel riuscire a fornire più informazioni possibili ai programmatori sulle caratteristiche della funzionalità da implementare. Se vuoi accelerare lo sviluppo, considera la possibilità di effettuare una donazione come descritto nella <application>&app;</application>Development.</para>
+        <para>R: Chiedi gentilmente. :-) Puoi presentare una richiesta qui <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=gnucash"/>. Ricorda di descrivere il più dettagliatamente possibile la caratteristica che vorresti vedere implementata. Il trucco sta tutto nel riuscire a fornire più informazioni possibili ai programmatori sulle caratteristiche della funzionalità da implementare. Se vuoi accelerare lo sviluppo, considera la possibilità di effettuare una donazione come descritto nella <application>&app;</application>Development.</para>
       </sect2>
 
       <sect2 id="appendixb_software_web">
@@ -12880,8 +12880,8 @@ work on earlier versions, too.</para>
 
       <sect2 id="appendixb_software_bugs">
         <title>D: Credo di aver trovato un bug. Come posso comunicarlo?</title>
-        <para>R: Prima di tutto, cerca di verificare che si tratti realmente di un bug e che non sia già stato messo in evidenza in passato. Cerca nell’archivio delle liste di discussione (vedi domanda più sopra). Poi passa a cercare in <ulink url="http://bugzilla.gnome.org">Gnome Bugzilla</ulink> database.</para>
-        <para>Se sei convinto di aver trovato realmente un nuovo bug, puoi comunicarlo all’indirizzo <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=gnucash"/>. Per favore ricorda di descrivere il bug con il massimo dettaglio possibile. Il trucco sta nel riuscire a fornire più informazioni possibili ai programmatori per riuscire a riprodurre il bug. Un programmatore è in genere in grado di risolvere un bug solo quando lo vede, se non riesci a mostrarlo al programmatore, non verrà tolto!</para>
+        <para>R: Prima di tutto, cerca di verificare che si tratti realmente di un bug e che non sia già stato messo in evidenza in passato. Cerca nell’archivio delle liste di discussione (vedi domanda più sopra). Poi passa a cercare in <ulink url="http://bugs.gnucash.org">&app; Bugzilla</ulink> database.</para>
+        <para>Se sei convinto di aver trovato realmente un nuovo bug, puoi comunicarlo all’indirizzo <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=gnucash"/>. Per favore ricorda di descrivere il bug con il massimo dettaglio possibile. Il trucco sta nel riuscire a fornire più informazioni possibili ai programmatori per riuscire a riprodurre il bug. Un programmatore è in genere in grado di risolvere un bug solo quando lo vede, se non riesci a mostrarlo al programmatore, non verrà tolto!</para>
       </sect2>
 
     </sect1>
diff --git a/guide/ja/appendixb.xml b/guide/ja/appendixb.xml
index 313c8a0..f13d8b9 100644
--- a/guide/ja/appendixb.xml
+++ b/guide/ja/appendixb.xml
@@ -75,7 +75,7 @@
 
       <sect2 id="appendixb_general_newFeatures">
         <title>Q: XYZ機能が本当に欲しいです。しかし&app;は持っていません。</title>
-        <para>A: うまくお願いしてください :-) エンハンス要望書を <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>に発行できます。エンハンス要望を可能な限り冗長に記述することを念頭においてください。ここの手段は、あなたが提案した新機能が行わなければならないことに関して最良情報をプログラマに提供する方法を学ぶことです。開発がかなり加速するように望んでいるなら、&app;Developmentで説明してあるようにいくらかの金銭の寄付を行うことを考えてください。</para>
+        <para>A: うまくお願いしてください :-) エンハンス要望書を <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>に発行できます。エンハンス要望を可能な限り冗長に記述することを念頭においてください。ここの手段は、あなたが提案した新機能が行わなければならないことに関して最良情報をプログラマに提供する方法を学ぶことです。開発がかなり加速するように望んでいるなら、&app;Developmentで説明してあるようにいくらかの金銭の寄付を行うことを考えてください。</para>
       </sect2>
 
       <sect2 id="appendixb_software_web">
@@ -95,8 +95,8 @@
 
       <sect2 id="appendixb_software_bugs">
         <title>Q: バグを見つけたようです。どうやってバグを報告しますか?</title>
-        <para>A: まず、本当に、それがバグであり、以前報告されたことがないことを確かめるようにします。メーリングリストアーカイブを検索してください (FAQの上部を参照)。後は、<ulink url="http://bugzilla.gnome.org">Gnome Bugzilla</ulink>データベースを検索します。</para>
-        <para>あなたが本当にバグを発見したと感じたら、後は  <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink> でそれを報告できます。可能な限り冗長に報告することを念頭においてください。ここの手段は、バグをどう再生させるかに関して最良情報をプログラマに提供する方法を学ぶことです。通常、プログラマは彼らが理解できるバグを修正できるだけです。あなたがプログラマにバグを理解させることができないなら、それは修正されません!</para>
+        <para>A: まず、本当に、それがバグであり、以前報告されたことがないことを確かめるようにします。メーリングリストアーカイブを検索してください (FAQの上部を参照)。後は、<ulink url="http://bugs.gnucash.org">&app; Bugzilla</ulink>データベースを検索します。</para>
+        <para>あなたが本当にバグを発見したと感じたら、後は  <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink> でそれを報告できます。可能な限り冗長に報告することを念頭においてください。ここの手段は、バグをどう再生させるかに関して最良情報をプログラマに提供する方法を学ぶことです。通常、プログラマは彼らが理解できるバグを修正できるだけです。あなたがプログラマにバグを理解させることができないなら、それは修正されません!</para>
       </sect2>
 
     </sect1>
diff --git a/guide/ja/gnucash-guide.xml b/guide/ja/gnucash-guide.xml
index d0a2644..577b413 100644
--- a/guide/ja/gnucash-guide.xml
+++ b/guide/ja/gnucash-guide.xml
@@ -228,7 +228,7 @@ Lyttle</holder> </copyright>
   </releaseinfo>
   <legalnotice>
     <title>フィードバック</title>
-      <para>本パッケージおよび本書に関してバグを報告する、または提案を行う際には <ulink url=" http://bugzilla.gnome.org
+      <para>本パッケージおよび本書に関してバグを報告する、または提案を行う際には <ulink url=" http://bugs.gnucash.org
 ">GNOME バグ追跡システム</ulink>を使用してください。
       </para>
 
diff --git a/guide/pt/appendixb.xml b/guide/pt/appendixb.xml
index e068149..81899de 100644
--- a/guide/pt/appendixb.xml
+++ b/guide/pt/appendixb.xml
@@ -123,7 +123,7 @@
         <title>P: Gostava realmente de ter a funcionalidade XYZ mas o <application>&app;</application> não 
         a tem. Como é que a posso adicionar?</title>
         <para>R: Peça com educação. :-) Pode fazer um pedido de melhoria em 
-        <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Por favor, lembre-se 
+        <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Por favor, lembre-se 
         de descrever a sua melhoria proposta de forma bastante completa. O truque aqui é aprender a dar a 
         melhor informação aos programadores sobre o que a sua melhoria proposta vai fazer. Se quer acelerar 
         o processo de desenvolvimento, considere doar algum dinheiro, conforme descrito em 
@@ -159,9 +159,9 @@
         <title>P: Penso que encontrei um erro. Como é que o reporto?</title>
         <para>R: Primeiro, tente verificar se é realmente um erro e se ainda não foi reportado. Procure 
         nos arquivos de correio (veja a FAQ acima). Depois procure na base de dados do  
-        <ulink url="http://bugzilla.gnome.org">Bugzilla do Gnome</ulink>.</para>
+        <ulink url="http://bugs.gnucash.org">Bugzilla do Gnome</ulink>.</para>
         <para>Se achar que realmente encontrou um novo erro, pode reportá-lo em 
-        <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Lembre-se de ser eloquente 
+        <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Lembre-se de ser eloquente 
         e claro. Tente aprender como deve informar os programadores a reproduzir o erro. Um programador só 
         consegue reparar um erro que consiga ver, se não o conseguir ver, o erro não será reparado.!</para>
       </sect2>
diff --git a/guide/pt/gnucash-guide.xml b/guide/pt/gnucash-guide.xml
index 06f13b2..9f4731d 100644
--- a/guide/pt/gnucash-guide.xml
+++ b/guide/pt/gnucash-guide.xml
@@ -339,7 +339,7 @@
   <legalnotice>
     <title>Comentários</title>
       <para>Para reportar um erro ou fazer uma sugestão a respeito deste pacote ou deste guia, siga as instruções no 
-      <ulink url="http://bugzilla.gnome.org">Sistema de rastreio de erros do GNOME</ulink>.
+      <ulink url="http://bugs.gnucash.org">Sistema de rastreio de erros do GNOME</ulink>.
       </para>
 <!-- Translators may also add here a feedback address for translations -->
   </legalnotice>
diff --git a/guide/ru/appendixb.xml b/guide/ru/appendixb.xml
index d13f60d..421b3cd 100644
--- a/guide/ru/appendixb.xml
+++ b/guide/ru/appendixb.xml
@@ -75,7 +75,7 @@
 
       <sect2 id="appendixb_general_newFeatures">
         <title>Q: I really want feature XYZ but <application>&app;</application> doesn’t have it. How do I get it added?</title>
-        <para>A: Ask nicely. :-) You can file an enhancement request at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to describe your proposed enhancement as verbosely as possible. The trick here is to learn how to give the best information to the programmers about what your proposed new feature should do. If you want to speed up development significantly, consider donating some money as described on <application>&app;</application>Development.</para>
+        <para>A: Ask nicely. :-) You can file an enhancement request at <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to describe your proposed enhancement as verbosely as possible. The trick here is to learn how to give the best information to the programmers about what your proposed new feature should do. If you want to speed up development significantly, consider donating some money as described on <application>&app;</application>Development.</para>
       </sect2>
 
       <sect2 id="appendixb_software_web">
@@ -95,8 +95,8 @@
 
       <sect2 id="appendixb_software_bugs">
         <title>Q: I think I found a bug. How do I report it?</title>
-        <para>A: First of all, try to verify that it is indeed a bug and that it has not been reported before. Search the mail list archives (see FAQ above). Then search the <ulink url="http://bugzilla.gnome.org">Gnome Bugzilla</ulink> database.</para>
-        <para>If you feel you have indeed found a bug, you can then report it at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to report your bug as verbosely as possible. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can’t make the programmer see your bug, it won’t get fixed!</para>
+        <para>A: First of all, try to verify that it is indeed a bug and that it has not been reported before. Search the mail list archives (see FAQ above). Then search the <ulink url="http://bugs.gnucash.org">&app; Bugzilla</ulink> database.</para>
+        <para>If you feel you have indeed found a bug, you can then report it at <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to report your bug as verbosely as possible. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can’t make the programmer see your bug, it won’t get fixed!</para>
       </sect2>
 
     </sect1>
diff --git a/guide/ru/gnucash-guide.xml b/guide/ru/gnucash-guide.xml
index 7fefcdd..185d485 100644
--- a/guide/ru/gnucash-guide.xml
+++ b/guide/ru/gnucash-guide.xml
@@ -364,8 +364,8 @@
     <title>Feedback</title>
       <para>To report a bug or make a suggestion regarding this package or
         this manual, follow the directions at the
-        <ulink url="http://bugzilla.gnome.org"
-          >GNOME Bug Tracking System</ulink>.
+        <ulink url="http://bugs.gnucash.org"
+          >&app; Bug Tracking System</ulink>.
       </para>
 <!-- Translators may also add here a feedback address for translations -->
   </legalnotice>
diff --git a/help/C/Help_tips-appendix.xml b/help/C/Help_tips-appendix.xml
index 9da00f2..b319af5 100644
--- a/help/C/Help_tips-appendix.xml
+++ b/help/C/Help_tips-appendix.xml
@@ -200,7 +200,7 @@
                                 <!-- <note><title>Known Issues</title>...</note> uses too much space-->
                               <para>Requires F::Q 1.41, but unfortunately the ASX website is only working sometimes.
                                 And then only with a small no of stocks in 1 go. From final comment on:
-                                <ulink url="https://bugzilla.gnome.org/show_bug.cgi?id=770132#c12">
+                                <ulink url="https://bugs.gnucash.org/show_bug.cgi?id=770132#c12">
                                 Price editor does not find ASX:XRO</ulink>
                               </para>
                             </entry>
@@ -860,7 +860,7 @@
 				src/engine/gnc-commodity.c:gnc_quote_source (commit c0fd3b3, which was
 				adjusted for Finance::Quote 1.47),
       			<ulink url="https://wiki.gnucash.org">&app;-Wiki</ulink>,
-				<ulink url="https://bugzilla.gnome.org/page.cgi?id=browse.html&product=GnuCash">bugzilla</ulink>,
+				<ulink url="https://bugs.gnucash.org/page.cgi?id=browse.html&product=GnuCash">bugzilla</ulink>,
 				<ulink url="https://wiki.gnucash.org/wiki/Mailing_Lists#Mailing_List_Archives">mailing list archive</ulink>.
 			</para>
 		</sect2>
diff --git a/help/C/gnucash-help.xml b/help/C/gnucash-help.xml
index 8c03ef6..5acb279 100644
--- a/help/C/gnucash-help.xml
+++ b/help/C/gnucash-help.xml
@@ -314,8 +314,8 @@
       <title>Feedback</title>
       <para>To report a bug or make a suggestion regarding this package or
         this manual, follow the directions at the
-        <ulink url="http://bugzilla.gnome.org"
-          >GNOME Bug Tracking System</ulink>.
+        <ulink url="http://bugs.gnucash.org"
+          >&app; Bug Tracking System</ulink>.
       </para>
 <!-- Translators may also add here feedback address for translations -->
     </legalnotice>
diff --git a/help/de/Help_tips-appendix.xml b/help/de/Help_tips-appendix.xml
index 041a68e..0c14bc3 100644
--- a/help/de/Help_tips-appendix.xml
+++ b/help/de/Help_tips-appendix.xml
@@ -200,7 +200,7 @@
                                 <!-- <note><title>Known Issues</title>...</note> uses too much space-->
                               <para>Requires F::Q 1.41, but unfortunately the ASX website is only working sometimes.
                                 And then only with a small no of stocks in 1 go. From final comment on:
-                                <ulink url="https://bugzilla.gnome.org/show_bug.cgi?id=770132#c12">
+                                <ulink url="https://bugs.gnucash.org/show_bug.cgi?id=770132#c12">
                                 Price editor does not find ASX:XRO</ulink>
                               </para>
                             </entry>
@@ -860,7 +860,7 @@
 				src/engine/gnc-commodity.c:gnc_quote_source (commit c0fd3b3, welche an
 				Finance::Quote 1.47 angepaßt wurde), 
       			<ulink url="https://wiki.gnucash.org">&app;-Wiki</ulink>,
-				<ulink url="https://bugzilla.gnome.org/page.cgi?id=browse.html&product=GnuCash">bugzilla</ulink>,
+				<ulink url="https://bugs.gnucash.org/page.cgi?id=browse.html&product=GnuCash">bugzilla</ulink>,
 				<ulink url="https://wiki.gnucash.org/wiki/Mailing_Lists#Mailing_List_Archives">Mailinglistenarchive</ulink>.
 			</para>
 		</sect2>
diff --git a/help/de/gnucash-help.xml b/help/de/gnucash-help.xml
index 5cf1608..855a00e 100644
--- a/help/de/gnucash-help.xml
+++ b/help/de/gnucash-help.xml
@@ -281,8 +281,8 @@
     <legalnotice>
       <title>Feedback</title>
       <para>Um Fehler zu berichten oder anderes Feedback zu geben, benutzen Sie
-        bitte das Gnome Bug-Tracking System
-        <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=GnuCash"
+        bitte das &app; Bug-Tracking System
+        <ulink url="http://bugs.gnucash.org/enter_bug.cgi?product=GnuCash"
           >Bugzilla</ulink>.
       </para>
 <!-- Translators may also add here feedback address for translations -->
@@ -4646,7 +4646,7 @@
           </listitem>
         </itemizedlist>
         <para />
-        <para>Die aktuell geöffnete Web-Seite wird im rechten Bereich des Hilfefensters angezeigt. Der linke Bereich enthält die Karteiseiten "Themen" und "Suchen". Wenn Sie auf der Karteiseite "Themen" ein Hilfethema auswählen, wird die entsprechende Web-Seite im rechten Bereich geladen. Die Liste der Hilfethemen enthält außerdem einen Link auf die GnuCash-Fehlerberichtsseite (http://bugzilla.gnome.org).</para>
+        <para>Die aktuell geöffnete Web-Seite wird im rechten Bereich des Hilfefensters angezeigt. Der linke Bereich enthält die Karteiseiten "Themen" und "Suchen". Wenn Sie auf der Karteiseite "Themen" ein Hilfethema auswählen, wird die entsprechende Web-Seite im rechten Bereich geladen. Die Liste der Hilfethemen enthält außerdem einen Link auf die GnuCash-Fehlerberichtsseite (http://bugs.gnucash.org).</para>
         <para />
         <para>Die Karteiseite "Suchen" ermöglicht es, die Hilfe nach Dokumenten zu durchsuchen, welche die von Ihnen angegebenen Begriffe enthalten. Geben Sie den zu suchenden Begriff im Feld "Suchausdruck" ein und betätigen Sie den Knopf "Suchen". Sie erhalten eine Liste der Seiten, welche diesen Begriff enthalten. Wenn Sie einen der gefundenen Verweise in der Liste "Suchergebnisse" anklicken, wird die entsprechende Web-Seite geladen.</para>
       </sect3>
diff --git a/help/it/gnucash-help.xml b/help/it/gnucash-help.xml
index 4ea28ca..a76ece1 100644
--- a/help/it/gnucash-help.xml
+++ b/help/it/gnucash-help.xml
@@ -386,7 +386,7 @@
     <releaseinfo>Questo manuale descrive l’utilizzo del programma finanziario &app;.</releaseinfo>
     <legalnotice>
       <title>Commenti</title>
-      <para>Per avvertire della presenza di un bug o per proporre dei suggerimenti a riguardo di questo programma o del manuale, seguire le istruzioni fornite nel <ulink url="http://bugzilla.gnome.org">sistema di tracciamento dei bug di GNOME</ulink>. Per contribuire alla traduzione del manuale segnalando eventuali errori, inviare un messaggio alla lista Italiana di <application>&app;</application> contattabile inviando una mail all’indirizzo <email>gnucash-it at gnucash.org</email></para>
+      <para>Per avvertire della presenza di un bug o per proporre dei suggerimenti a riguardo di questo programma o del manuale, seguire le istruzioni fornite nel <ulink url="http://bugs.gnucash.org">sistema di tracciamento dei bug di GNOME</ulink>. Per contribuire alla traduzione del manuale segnalando eventuali errori, inviare un messaggio alla lista Italiana di <application>&app;</application> contattabile inviando una mail all’indirizzo <email>gnucash-it at gnucash.org</email></para>
 <!-- Translators may also add here feedback address for translations -->
     </legalnotice>
 
diff --git a/help/pt/gnucash-help.xml b/help/pt/gnucash-help.xml
index c0458ad..b1df640 100644
--- a/help/pt/gnucash-help.xml
+++ b/help/pt/gnucash-help.xml
@@ -280,7 +280,7 @@
       <title>Comentários</title>
       <para>Para reportar um erro ou fazer sugestões sobre este pacote ou este 
         manual, siga as instruções no 
-        <ulink url="http://bugzilla.gnome.org">Sistema de rastreio de erros do GNOME</ulink>.
+        <ulink url="http://bugs.gnucash.org">Sistema de rastreio de erros do GNOME</ulink>.
       </para>
 <!-- Translators may also add here feedback address for translations -->
     </legalnotice>



Summary of changes:
 guide/C/appendixb.xml          | 6 +++---
 guide/C/gnucash-guide.xml      | 4 ++--
 guide/de/appendixb.xml         | 6 +++---
 guide/de/gnucash-guide.xml     | 4 ++--
 guide/it/gnucash-guide.xml     | 8 ++++----
 guide/ja/appendixb.xml         | 6 +++---
 guide/ja/gnucash-guide.xml     | 2 +-
 guide/pt/appendixb.xml         | 6 +++---
 guide/pt/gnucash-guide.xml     | 2 +-
 guide/ru/appendixb.xml         | 6 +++---
 guide/ru/gnucash-guide.xml     | 4 ++--
 help/C/Help_tips-appendix.xml  | 4 ++--
 help/C/gnucash-help.xml        | 4 ++--
 help/de/Help_tips-appendix.xml | 4 ++--
 help/de/gnucash-help.xml       | 6 +++---
 help/it/gnucash-help.xml       | 2 +-
 help/pt/gnucash-help.xml       | 2 +-
 17 files changed, 38 insertions(+), 38 deletions(-)



More information about the gnucash-changes mailing list