From 62ae9ff91bdcdf5ff0ab0a495dd507bf7b1c83b1 Mon Sep 17 00:00:00 2001 From: Bob Swift Date: Wed, 20 Sep 2023 10:59:50 -0600 Subject: [PATCH 1/3] Update to include details on gettings logs, normally and when crash --- troubleshooting/troubleshooting.rst | 85 +++++++++++++++++++++++------ 1 file changed, 68 insertions(+), 17 deletions(-) diff --git a/troubleshooting/troubleshooting.rst b/troubleshooting/troubleshooting.rst index caec1a75b..80e0febfe 100644 --- a/troubleshooting/troubleshooting.rst +++ b/troubleshooting/troubleshooting.rst @@ -21,36 +21,87 @@ If you have problems using Picard, please first check the following resources: :index:`Reporting a Bug ` ------------------------------------------------------------ -If you think you have found a bug please check whether you are using the latest version of Picard and whether the -bug has already been reported in the `bug tracker `_. If you're not -sure or don't want to look through the existing tickets, ask on the community forums first. +If you think you have found a bug please check whether you are using the latest version of Picard and whether the bug has already been reported in the `bug tracker `_. If you're not sure or don't want to look through the existing tickets, ask on the community forums first. -If you're still convinced you have found a new bug, open a `new ticket -`_ providing the following information: +If you're still convinced you have found a new bug, open a `new ticket `_ providing the following information: * Which version of Picard do you use? ("Affects Version" in the form) * Which operating system do you use? ("Environment" in the form) * What did you do when the bug occurred? -* What actually happened and what did you expect to happen? +* What actually happened, and what did you expect to happen? * If you're using plugins, which plugins do you have enabled? +* The **"Debug"** level log from the Picard session demonstrating the problem. +.. warning:: -:index:`Getting Logs ` ----------------------------------------------- + Please remember to first remove any personal and confidential information like user id, passwords or authorization tokens before posting or submitting any log output. -For many bugs, it helps developers to have a log from Picard. You can see the log by going to :menuselection:`"Help --> View Log"`. -You can also get a full debug log (better because it contains more detailed information) by starting Picard with :option:`-d` as a -command-line argument. If you're using Windows, you can change your shortcut's Target (:menuselection:`right click shortcut --> -Properties`) to:: - "C:\Program Files\MusicBrainz Picard\picard.exe" -d +:index:`Getting a Debug Log ` +------------------------------------------------------------- -Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly. +For many bugs, it helps developers to have a log from Picard. You can see the log by going to :menuselection:`"Help --> View Log"`. You can also get a full debug log, which is better because it contains more detailed information. Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly. To retrieve the full debug log: -.. warning:: +1. Start Picard. +2. Open the log view with :menuselection:`"Help --> View Log"`. +3. Change the log level :guilabel:`verbosity` to **Debug**. +4. Close the log viewer. +5. Close and restart Picard. +6. Repeat the action that caused the problem being reported. +7. Open the log viewer and copy the output to paste into the forum post or bug ticket. Alternately, you can save the log to a file to attach to your bug report by using the :guilabel:`Save As...` button. +8. Close the log viewer, and close Picard. + + +:index:`Getting Logs in Case of Crashes ` +----------------------------------------------------------------------------------- + +In some cases the problem will cause Picard to crash and not allow you to access the resulting log from the log viewer. You can still generate a log output to attach to your report by starting Picard with the ``-d`` command line option from a command / terminal window and copying the information output to the terminal. The steps to follow for each of the supported platforms are: + +Windows Systems ++++++++++++++++ + +First open a command window by clicking the search icon on the Windows Taskbar and enter "cmd". Then start Picard by entering the following in the command window: + +.. code:: + + "C:\Program Files\MusicBrainz Picard\picard.exe" -d + +This will display all log information in the command window, and allow you to copy the information to the clipboard to paste into your report. + +.. note:: + + This method will only work with the installed version of Picard. It will not work with the portable version. + + +macOS Systems ++++++++++++++ + +First open a terminal window by doing one of the following: + +- Click the Launchpad icon in the Dock, type "Terminal" in the search field, then click :guilabel:`Terminal`. + +- In the Finder, open the "/Applications/Utilities" folder, then double-click "Terminal". + +Assuming Picard was put into the system wide Applications folder when installed, it can then be started by entering the following in the terminal window: + +.. code:: + + "/Applications/MusicBrainz Picard.app/Contents/MacOS/picard-run" --debug + +This will display all log information in the terminal window, and allow you to copy the information to the clipboard to paste into your report. + + +Linux Systems ++++++++++++++ + +First open a Terminal window. Then start Picard by entering the following in the terminal window: + +.. code:: + + picard -d + +This will display all log information in the terminal window, and allow you to copy the information to the clipboard to paste into your report. - Please remember to first remove any personal and confidential information like user id, passwords or authorization tokens - before posting or submitting any log output. .. only:: html and not epub From 77fc04dbbc8c1f221eb194c335e6e1ffad183c2e Mon Sep 17 00:00:00 2001 From: Bob Swift Date: Wed, 20 Sep 2023 15:59:05 -0600 Subject: [PATCH 2/3] Fix typo and some wording changes to help clarify --- troubleshooting/troubleshooting.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/troubleshooting/troubleshooting.rst b/troubleshooting/troubleshooting.rst index 80e0febfe..46b0678b0 100644 --- a/troubleshooting/troubleshooting.rst +++ b/troubleshooting/troubleshooting.rst @@ -40,7 +40,7 @@ If you're still convinced you have found a new bug, open a `new ticket ` ------------------------------------------------------------- -For many bugs, it helps developers to have a log from Picard. You can see the log by going to :menuselection:`"Help --> View Log"`. You can also get a full debug log, which is better because it contains more detailed information. Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly. To retrieve the full debug log: +For many bugs, it helps developers to have a debug log from Picard. You can see the log by going to :menuselection:`"Help --> View Log"`. You can also get a full debug log, which is better because it contains more detailed information. Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly. To retrieve the full debug log: 1. Start Picard. 2. Open the log view with :menuselection:`"Help --> View Log"`. @@ -52,10 +52,10 @@ For many bugs, it helps developers to have a log from Picard. You can see the lo 8. Close the log viewer, and close Picard. -:index:`Getting Logs in Case of Crashes ` +:index:`Getting Logs in Case of Crashes ` ----------------------------------------------------------------------------------- -In some cases the problem will cause Picard to crash and not allow you to access the resulting log from the log viewer. You can still generate a log output to attach to your report by starting Picard with the ``-d`` command line option from a command / terminal window and copying the information output to the terminal. The steps to follow for each of the supported platforms are: +In some cases the problem will cause Picard to crash and not allow you to access the resulting log from the log viewer. You can still generate a log output to attach to your report by starting Picard with the ``--debug`` command line option from a command / terminal window and copying the log output information from the terminal. The steps to follow for each of the supported platforms are: Windows Systems +++++++++++++++ @@ -64,13 +64,13 @@ First open a command window by clicking the search icon on the Windows Taskbar a .. code:: - "C:\Program Files\MusicBrainz Picard\picard.exe" -d + "C:\Program Files\MusicBrainz Picard\picard.exe" --debug -This will display all log information in the command window, and allow you to copy the information to the clipboard to paste into your report. +This will display all log entries in the command window, and allow you to copy the information to the clipboard to paste into your report. .. note:: - This method will only work with the installed version of Picard. It will not work with the portable version. + This method will only work with the installed version of Picard. It will not work with the portable or Windows Store versions. macOS Systems @@ -88,19 +88,19 @@ Assuming Picard was put into the system wide Applications folder when installed, "/Applications/MusicBrainz Picard.app/Contents/MacOS/picard-run" --debug -This will display all log information in the terminal window, and allow you to copy the information to the clipboard to paste into your report. +This will display all log entries in the terminal window, and allow you to copy the information to the clipboard to paste into your report. Linux Systems +++++++++++++ -First open a Terminal window. Then start Picard by entering the following in the terminal window: +First open a Terminal window in your desktop environment, either from the Applications menu or by pressing :kbd:`Ctrl+Alt+T` on most systems. Then start Picard by entering the following in the terminal window: .. code:: - picard -d + picard --debug -This will display all log information in the terminal window, and allow you to copy the information to the clipboard to paste into your report. +This will display all log entries in the terminal window, and allow you to copy the information to the clipboard to paste into your report. .. only:: html and not epub From a9d983f129f4838566ee9787f067b2956b79e57b Mon Sep 17 00:00:00 2001 From: Bob Swift Date: Fri, 22 Sep 2023 08:58:56 -0600 Subject: [PATCH 3/3] Update translation files --- .../troubleshooting/troubleshooting.po | 163 +++++++++++++-- .../troubleshooting/troubleshooting.po | 188 +++++++++++++++--- .../troubleshooting/troubleshooting.pot | 119 +++++++++-- .../troubleshooting/troubleshooting.po | 163 +++++++++++++-- .../troubleshooting/troubleshooting.po | 163 +++++++++++++-- .../troubleshooting/troubleshooting.po | 163 +++++++++++++-- 6 files changed, 826 insertions(+), 133 deletions(-) diff --git a/_locale/de/LC_MESSAGES/troubleshooting/troubleshooting.po b/_locale/de/LC_MESSAGES/troubleshooting/troubleshooting.po index c1b5f7632..1c1adde6d 100644 --- a/_locale/de/LC_MESSAGES/troubleshooting/troubleshooting.po +++ b/_locale/de/LC_MESSAGES/troubleshooting/troubleshooting.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: MusicBrainz Picard v2.6.3\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-14 08:09+0100\n" +"POT-Creation-Date: 2023-09-22 08:57-0600\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -75,61 +75,180 @@ msgid "" "the community forums first." msgstr "" -#: ../../troubleshooting/troubleshooting.rst:28 +#: ../../troubleshooting/troubleshooting.rst:26 msgid "" "If you're still convinced you have found a new bug, open a `new ticket " "`_ providing the following information:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:31 +#: ../../troubleshooting/troubleshooting.rst:28 msgid "Which version of Picard do you use? (\"Affects Version\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:32 +#: ../../troubleshooting/troubleshooting.rst:29 msgid "Which operating system do you use? (\"Environment\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:33 +#: ../../troubleshooting/troubleshooting.rst:30 msgid "What did you do when the bug occurred?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:34 -msgid "What actually happened and what did you expect to happen?" +#: ../../troubleshooting/troubleshooting.rst:31 +msgid "What actually happened, and what did you expect to happen?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:35 +#: ../../troubleshooting/troubleshooting.rst:32 msgid "If you're using plugins, which plugins do you have enabled?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:39 -msgid ":index:`Getting Logs `" +#: ../../troubleshooting/troubleshooting.rst:33 +msgid "" +"The **\"Debug\"** level log from the Picard session demonstrating the " +"problem." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:37 +msgid "" +"Please remember to first remove any personal and confidential information " +"like user id, passwords or authorization tokens before posting or submitting " +"any log output." msgstr "" #: ../../troubleshooting/troubleshooting.rst:41 +msgid ":index:`Getting a Debug Log `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:43 msgid "" -"For many bugs, it helps developers to have a log from Picard. You can see " -"the log by going to :menuselection:`\"Help --> View Log\"`. You can also get " -"a full debug log (better because it contains more detailed information) by " -"starting Picard with :option:`-d` as a command-line argument. If you're " -"using Windows, you can change your shortcut's Target (:menuselection:`right " -"click shortcut --> Properties`) to::" +"For many bugs, it helps developers to have a debug log from Picard. You can " +"see the log by going to :menuselection:`\"Help --> View Log\"`. You can also " +"get a full debug log, which is better because it contains more detailed " +"information. Pasting this log into your forum post or bug ticket can help " +"developers and other users to resolve your issue more quickly. To retrieve " +"the full debug log:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:45 +msgid "Start Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:46 +msgid "Open the log view with :menuselection:`\"Help --> View Log\"`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:47 +msgid "Change the log level :guilabel:`verbosity` to **Debug**." msgstr "" #: ../../troubleshooting/troubleshooting.rst:48 +msgid "Close the log viewer." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:49 +msgid "Close and restart Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:50 +msgid "Repeat the action that caused the problem being reported." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:51 msgid "" -"Pasting this log into your forum post or bug ticket can help developers and " -"other users to resolve your issue more quickly." +"Open the log viewer and copy the output to paste into the forum post or bug " +"ticket. Alternately, you can save the log to a file to attach to your bug " +"report by using the :guilabel:`Save As...` button." msgstr "" #: ../../troubleshooting/troubleshooting.rst:52 +msgid "Close the log viewer, and close Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:56 msgid "" -"Please remember to first remove any personal and confidential information " -"like user id, passwords or authorization tokens before posting or submitting " -"any log output." +":index:`Getting Logs in Case of Crashes `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:58 +msgid "" +"In some cases the problem will cause Picard to crash and not allow you to " +"access the resulting log from the log viewer. You can still generate a log " +"output to attach to your report by starting Picard with the ``--debug`` " +"command line option from a command / terminal window and copying the log " +"output information from the terminal. The steps to follow for each of the " +"supported platforms are:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:61 +msgid "Windows Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:63 +msgid "" +"First open a command window by clicking the search icon on the Windows " +"Taskbar and enter \"cmd\". Then start Picard by entering the following in " +"the command window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:69 +msgid "" +"This will display all log entries in the command window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:73 +msgid "" +"This method will only work with the installed version of Picard. It will " +"not work with the portable or Windows Store versions." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:77 +msgid "macOS Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:79 +msgid "First open a terminal window by doing one of the following:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:81 +msgid "" +"Click the Launchpad icon in the Dock, type \"Terminal\" in the search field, " +"then click :guilabel:`Terminal`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:83 +msgid "" +"In the Finder, open the \"/Applications/Utilities\" folder, then double-" +"click \"Terminal\"." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:85 +msgid "" +"Assuming Picard was put into the system wide Applications folder when " +"installed, it can then be started by entering the following in the terminal " +"window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:91 +#: ../../troubleshooting/troubleshooting.rst:103 +msgid "" +"This will display all log entries in the terminal window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:95 +msgid "Linux Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:97 +msgid "" +"First open a Terminal window in your desktop environment, either from the " +"Applications menu or by pressing :kbd:`Ctrl+Alt+T` on most systems. Then " +"start Picard by entering the following in the terminal window:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:59 +#: ../../troubleshooting/troubleshooting.rst:110 msgid "" "Specific situations: :doc:`does_not_start` / :doc:`no_coverart` / :doc:" "`missing_tags` / :doc:`not_saving` / :doc:`stopped_working` / :doc:" diff --git a/_locale/fr/LC_MESSAGES/troubleshooting/troubleshooting.po b/_locale/fr/LC_MESSAGES/troubleshooting/troubleshooting.po index 47d56066f..5e9e30357 100644 --- a/_locale/fr/LC_MESSAGES/troubleshooting/troubleshooting.po +++ b/_locale/fr/LC_MESSAGES/troubleshooting/troubleshooting.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: MusicBrainz Picard v2.3.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-14 08:09+0100\n" +"POT-Creation-Date: 2023-09-22 08:57-0600\n" "PO-Revision-Date: 2022-05-04 13:10-0600\n" "Last-Translator: Bob Swift \n" "Language-Team: \n" @@ -95,7 +95,7 @@ msgstr "" "pas sûr ou ne souhaitez pas consulter les tickets existants, demandez " "d'abord sur les forums de la communauté." -#: ../../troubleshooting/troubleshooting.rst:28 +#: ../../troubleshooting/troubleshooting.rst:26 msgid "" "If you're still convinced you have found a new bug, open a `new ticket " "`_ fournissant les informations suivantes:" -#: ../../troubleshooting/troubleshooting.rst:31 +#: ../../troubleshooting/troubleshooting.rst:28 msgid "Which version of Picard do you use? (\"Affects Version\" in the form)" msgstr "" "Quelle version de Picard utilisez-vous? (\"Affecte la version\" dans le " "formulaire)" -#: ../../troubleshooting/troubleshooting.rst:32 +#: ../../troubleshooting/troubleshooting.rst:29 msgid "Which operating system do you use? (\"Environment\" in the form)" msgstr "" "Quel système d'exploitation utilisez-vous? (\"Environnement\" dans le " "formulaire)" -#: ../../troubleshooting/troubleshooting.rst:33 +#: ../../troubleshooting/troubleshooting.rst:30 msgid "What did you do when the bug occurred?" msgstr "Qu'avez-vous fait lorsque le bogue est survenu?" -#: ../../troubleshooting/troubleshooting.rst:34 -msgid "What actually happened and what did you expect to happen?" +#: ../../troubleshooting/troubleshooting.rst:31 +#, fuzzy +msgid "What actually happened, and what did you expect to happen?" msgstr "Que s'est-il réellement passé et à quoi vous attendiez-vous?" -#: ../../troubleshooting/troubleshooting.rst:35 +#: ../../troubleshooting/troubleshooting.rst:32 msgid "If you're using plugins, which plugins do you have enabled?" msgstr "Si vous utilisez des plugins, quels plugins avez-vous activés?" -#: ../../troubleshooting/troubleshooting.rst:39 -msgid ":index:`Getting Logs `" -msgstr ":index:`Récupération des journaux `" +#: ../../troubleshooting/troubleshooting.rst:33 +msgid "" +"The **\"Debug\"** level log from the Picard session demonstrating the " +"problem." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:37 +msgid "" +"Please remember to first remove any personal and confidential information " +"like user id, passwords or authorization tokens before posting or submitting " +"any log output." +msgstr "" +"N'oubliez pas de supprimer d'abord toutes les informations personnelles et " +"confidentielles telles que l'identifiant d'utilisateur, les mots de passe ou " +"les jetons d'autorisation avant de publier ou de soumettre une sortie de " +"journal." #: ../../troubleshooting/troubleshooting.rst:41 +#, fuzzy +msgid ":index:`Getting a Debug Log `" +msgstr ":index:`Récupération des journaux `" + +#: ../../troubleshooting/troubleshooting.rst:43 +#, fuzzy msgid "" -"For many bugs, it helps developers to have a log from Picard. You can see " -"the log by going to :menuselection:`\"Help --> View Log\"`. You can also get " -"a full debug log (better because it contains more detailed information) by " -"starting Picard with :option:`-d` as a command-line argument. If you're " -"using Windows, you can change your shortcut's Target (:menuselection:`right " -"click shortcut --> Properties`) to::" +"For many bugs, it helps developers to have a debug log from Picard. You can " +"see the log by going to :menuselection:`\"Help --> View Log\"`. You can also " +"get a full debug log, which is better because it contains more detailed " +"information. Pasting this log into your forum post or bug ticket can help " +"developers and other users to resolve your issue more quickly. To retrieve " +"the full debug log:" msgstr "" "Pour de nombreux bogues, cela aide les développeurs à avoir un journal de " "Picard. Vous pouvez voir le journal en allant dans :menuselection:`\"Aide --" @@ -150,27 +170,127 @@ msgstr "" "vous utilisez Windows, vous pouvez modifier la cible de votre raccourci (:" "menuselection:`raccourci clic droit --> Propriétés`) en::" +#: ../../troubleshooting/troubleshooting.rst:45 +msgid "Start Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:46 +msgid "Open the log view with :menuselection:`\"Help --> View Log\"`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:47 +msgid "Change the log level :guilabel:`verbosity` to **Debug**." +msgstr "" + #: ../../troubleshooting/troubleshooting.rst:48 +msgid "Close the log viewer." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:49 +msgid "Close and restart Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:50 +msgid "Repeat the action that caused the problem being reported." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:51 msgid "" -"Pasting this log into your forum post or bug ticket can help developers and " -"other users to resolve your issue more quickly." +"Open the log viewer and copy the output to paste into the forum post or bug " +"ticket. Alternately, you can save the log to a file to attach to your bug " +"report by using the :guilabel:`Save As...` button." msgstr "" -"Le fait de coller ce journal dans votre message de forum ou votre ticket de " -"bogue peut aider les développeurs et les autres utilisateurs à résoudre " -"votre problème plus rapidement." #: ../../troubleshooting/troubleshooting.rst:52 +msgid "Close the log viewer, and close Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:56 +#, fuzzy msgid "" -"Please remember to first remove any personal and confidential information " -"like user id, passwords or authorization tokens before posting or submitting " -"any log output." +":index:`Getting Logs in Case of Crashes `" +msgstr ":index:`Récupération des journaux `" + +#: ../../troubleshooting/troubleshooting.rst:58 +msgid "" +"In some cases the problem will cause Picard to crash and not allow you to " +"access the resulting log from the log viewer. You can still generate a log " +"output to attach to your report by starting Picard with the ``--debug`` " +"command line option from a command / terminal window and copying the log " +"output information from the terminal. The steps to follow for each of the " +"supported platforms are:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:61 +msgid "Windows Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:63 +msgid "" +"First open a command window by clicking the search icon on the Windows " +"Taskbar and enter \"cmd\". Then start Picard by entering the following in " +"the command window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:69 +msgid "" +"This will display all log entries in the command window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:73 +msgid "" +"This method will only work with the installed version of Picard. It will " +"not work with the portable or Windows Store versions." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:77 +msgid "macOS Systems" msgstr "" -"N'oubliez pas de supprimer d'abord toutes les informations personnelles et " -"confidentielles telles que l'identifiant d'utilisateur, les mots de passe ou " -"les jetons d'autorisation avant de publier ou de soumettre une sortie de " -"journal." -#: ../../troubleshooting/troubleshooting.rst:59 +#: ../../troubleshooting/troubleshooting.rst:79 +msgid "First open a terminal window by doing one of the following:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:81 +msgid "" +"Click the Launchpad icon in the Dock, type \"Terminal\" in the search field, " +"then click :guilabel:`Terminal`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:83 +msgid "" +"In the Finder, open the \"/Applications/Utilities\" folder, then double-" +"click \"Terminal\"." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:85 +msgid "" +"Assuming Picard was put into the system wide Applications folder when " +"installed, it can then be started by entering the following in the terminal " +"window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:91 +#: ../../troubleshooting/troubleshooting.rst:103 +msgid "" +"This will display all log entries in the terminal window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:95 +msgid "Linux Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:97 +msgid "" +"First open a Terminal window in your desktop environment, either from the " +"Applications menu or by pressing :kbd:`Ctrl+Alt+T` on most systems. Then " +"start Picard by entering the following in the terminal window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:110 msgid "" "Specific situations: :doc:`does_not_start` / :doc:`no_coverart` / :doc:" "`missing_tags` / :doc:`not_saving` / :doc:`stopped_working` / :doc:" @@ -180,6 +300,14 @@ msgstr "" "`missing_tags` / :doc:`not_saving` / :doc:`stopped_working` / :doc:" "`macos_startup_error`" +#~ msgid "" +#~ "Pasting this log into your forum post or bug ticket can help developers " +#~ "and other users to resolve your issue more quickly." +#~ msgstr "" +#~ "Le fait de coller ce journal dans votre message de forum ou votre ticket " +#~ "de bogue peut aider les développeurs et les autres utilisateurs à " +#~ "résoudre votre problème plus rapidement." + #~ msgid "General Troubleshooting" #~ msgstr "Dépannage général" diff --git a/_locale/gettext/troubleshooting/troubleshooting.pot b/_locale/gettext/troubleshooting/troubleshooting.pot index 152d93222..0f7aeeff9 100644 --- a/_locale/gettext/troubleshooting/troubleshooting.pot +++ b/_locale/gettext/troubleshooting/troubleshooting.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: MusicBrainz Picard v2.9alpha1\n" +"Project-Id-Version: MusicBrainz Picard v2.9.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-14 08:09+0100\n" +"POT-Creation-Date: 2023-09-22 08:57-0600\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -56,46 +56,135 @@ msgstr "" msgid "If you think you have found a bug please check whether you are using the latest version of Picard and whether the bug has already been reported in the `bug tracker `_. If you're not sure or don't want to look through the existing tickets, ask on the community forums first." msgstr "" -#: ../../troubleshooting/troubleshooting.rst:28 +#: ../../troubleshooting/troubleshooting.rst:26 msgid "If you're still convinced you have found a new bug, open a `new ticket `_ providing the following information:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:31 +#: ../../troubleshooting/troubleshooting.rst:28 msgid "Which version of Picard do you use? (\"Affects Version\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:32 +#: ../../troubleshooting/troubleshooting.rst:29 msgid "Which operating system do you use? (\"Environment\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:33 +#: ../../troubleshooting/troubleshooting.rst:30 msgid "What did you do when the bug occurred?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:34 -msgid "What actually happened and what did you expect to happen?" +#: ../../troubleshooting/troubleshooting.rst:31 +msgid "What actually happened, and what did you expect to happen?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:35 +#: ../../troubleshooting/troubleshooting.rst:32 msgid "If you're using plugins, which plugins do you have enabled?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:39 -msgid ":index:`Getting Logs `" +#: ../../troubleshooting/troubleshooting.rst:33 +msgid "The **\"Debug\"** level log from the Picard session demonstrating the problem." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:37 +msgid "Please remember to first remove any personal and confidential information like user id, passwords or authorization tokens before posting or submitting any log output." msgstr "" #: ../../troubleshooting/troubleshooting.rst:41 -msgid "For many bugs, it helps developers to have a log from Picard. You can see the log by going to :menuselection:`\"Help --> View Log\"`. You can also get a full debug log (better because it contains more detailed information) by starting Picard with :option:`-d` as a command-line argument. If you're using Windows, you can change your shortcut's Target (:menuselection:`right click shortcut --> Properties`) to::" +msgid ":index:`Getting a Debug Log `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:43 +msgid "For many bugs, it helps developers to have a debug log from Picard. You can see the log by going to :menuselection:`\"Help --> View Log\"`. You can also get a full debug log, which is better because it contains more detailed information. Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly. To retrieve the full debug log:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:45 +msgid "Start Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:46 +msgid "Open the log view with :menuselection:`\"Help --> View Log\"`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:47 +msgid "Change the log level :guilabel:`verbosity` to **Debug**." msgstr "" #: ../../troubleshooting/troubleshooting.rst:48 -msgid "Pasting this log into your forum post or bug ticket can help developers and other users to resolve your issue more quickly." +msgid "Close the log viewer." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:49 +msgid "Close and restart Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:50 +msgid "Repeat the action that caused the problem being reported." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:51 +msgid "Open the log viewer and copy the output to paste into the forum post or bug ticket. Alternately, you can save the log to a file to attach to your bug report by using the :guilabel:`Save As...` button." msgstr "" #: ../../troubleshooting/troubleshooting.rst:52 -msgid "Please remember to first remove any personal and confidential information like user id, passwords or authorization tokens before posting or submitting any log output." +msgid "Close the log viewer, and close Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:56 +msgid ":index:`Getting Logs in Case of Crashes `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:58 +msgid "In some cases the problem will cause Picard to crash and not allow you to access the resulting log from the log viewer. You can still generate a log output to attach to your report by starting Picard with the ``--debug`` command line option from a command / terminal window and copying the log output information from the terminal. The steps to follow for each of the supported platforms are:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:61 +msgid "Windows Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:63 +msgid "First open a command window by clicking the search icon on the Windows Taskbar and enter \"cmd\". Then start Picard by entering the following in the command window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:69 +msgid "This will display all log entries in the command window, and allow you to copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:73 +msgid "This method will only work with the installed version of Picard. It will not work with the portable or Windows Store versions." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:77 +msgid "macOS Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:79 +msgid "First open a terminal window by doing one of the following:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:81 +msgid "Click the Launchpad icon in the Dock, type \"Terminal\" in the search field, then click :guilabel:`Terminal`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:83 +msgid "In the Finder, open the \"/Applications/Utilities\" folder, then double-click \"Terminal\"." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:85 +msgid "Assuming Picard was put into the system wide Applications folder when installed, it can then be started by entering the following in the terminal window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:91 +#: ../../troubleshooting/troubleshooting.rst:103 +msgid "This will display all log entries in the terminal window, and allow you to copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:95 +msgid "Linux Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:97 +msgid "First open a Terminal window in your desktop environment, either from the Applications menu or by pressing :kbd:`Ctrl+Alt+T` on most systems. Then start Picard by entering the following in the terminal window:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:59 +#: ../../troubleshooting/troubleshooting.rst:110 msgid "Specific situations: :doc:`does_not_start` / :doc:`no_coverart` / :doc:`missing_tags` / :doc:`not_saving` / :doc:`stopped_working` / :doc:`macos_startup_error`" msgstr "" diff --git a/_locale/nb_NO/LC_MESSAGES/troubleshooting/troubleshooting.po b/_locale/nb_NO/LC_MESSAGES/troubleshooting/troubleshooting.po index 11b06d5a6..8798fa63b 100644 --- a/_locale/nb_NO/LC_MESSAGES/troubleshooting/troubleshooting.po +++ b/_locale/nb_NO/LC_MESSAGES/troubleshooting/troubleshooting.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: MusicBrainz Picard v2.7.0b1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-14 08:09+0100\n" +"POT-Creation-Date: 2023-09-22 08:57-0600\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -75,61 +75,180 @@ msgid "" "the community forums first." msgstr "" -#: ../../troubleshooting/troubleshooting.rst:28 +#: ../../troubleshooting/troubleshooting.rst:26 msgid "" "If you're still convinced you have found a new bug, open a `new ticket " "`_ providing the following information:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:31 +#: ../../troubleshooting/troubleshooting.rst:28 msgid "Which version of Picard do you use? (\"Affects Version\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:32 +#: ../../troubleshooting/troubleshooting.rst:29 msgid "Which operating system do you use? (\"Environment\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:33 +#: ../../troubleshooting/troubleshooting.rst:30 msgid "What did you do when the bug occurred?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:34 -msgid "What actually happened and what did you expect to happen?" +#: ../../troubleshooting/troubleshooting.rst:31 +msgid "What actually happened, and what did you expect to happen?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:35 +#: ../../troubleshooting/troubleshooting.rst:32 msgid "If you're using plugins, which plugins do you have enabled?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:39 -msgid ":index:`Getting Logs `" +#: ../../troubleshooting/troubleshooting.rst:33 +msgid "" +"The **\"Debug\"** level log from the Picard session demonstrating the " +"problem." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:37 +msgid "" +"Please remember to first remove any personal and confidential information " +"like user id, passwords or authorization tokens before posting or submitting " +"any log output." msgstr "" #: ../../troubleshooting/troubleshooting.rst:41 +msgid ":index:`Getting a Debug Log `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:43 msgid "" -"For many bugs, it helps developers to have a log from Picard. You can see " -"the log by going to :menuselection:`\"Help --> View Log\"`. You can also get " -"a full debug log (better because it contains more detailed information) by " -"starting Picard with :option:`-d` as a command-line argument. If you're " -"using Windows, you can change your shortcut's Target (:menuselection:`right " -"click shortcut --> Properties`) to::" +"For many bugs, it helps developers to have a debug log from Picard. You can " +"see the log by going to :menuselection:`\"Help --> View Log\"`. You can also " +"get a full debug log, which is better because it contains more detailed " +"information. Pasting this log into your forum post or bug ticket can help " +"developers and other users to resolve your issue more quickly. To retrieve " +"the full debug log:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:45 +msgid "Start Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:46 +msgid "Open the log view with :menuselection:`\"Help --> View Log\"`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:47 +msgid "Change the log level :guilabel:`verbosity` to **Debug**." msgstr "" #: ../../troubleshooting/troubleshooting.rst:48 +msgid "Close the log viewer." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:49 +msgid "Close and restart Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:50 +msgid "Repeat the action that caused the problem being reported." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:51 msgid "" -"Pasting this log into your forum post or bug ticket can help developers and " -"other users to resolve your issue more quickly." +"Open the log viewer and copy the output to paste into the forum post or bug " +"ticket. Alternately, you can save the log to a file to attach to your bug " +"report by using the :guilabel:`Save As...` button." msgstr "" #: ../../troubleshooting/troubleshooting.rst:52 +msgid "Close the log viewer, and close Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:56 msgid "" -"Please remember to first remove any personal and confidential information " -"like user id, passwords or authorization tokens before posting or submitting " -"any log output." +":index:`Getting Logs in Case of Crashes `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:58 +msgid "" +"In some cases the problem will cause Picard to crash and not allow you to " +"access the resulting log from the log viewer. You can still generate a log " +"output to attach to your report by starting Picard with the ``--debug`` " +"command line option from a command / terminal window and copying the log " +"output information from the terminal. The steps to follow for each of the " +"supported platforms are:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:61 +msgid "Windows Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:63 +msgid "" +"First open a command window by clicking the search icon on the Windows " +"Taskbar and enter \"cmd\". Then start Picard by entering the following in " +"the command window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:69 +msgid "" +"This will display all log entries in the command window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:73 +msgid "" +"This method will only work with the installed version of Picard. It will " +"not work with the portable or Windows Store versions." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:77 +msgid "macOS Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:79 +msgid "First open a terminal window by doing one of the following:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:81 +msgid "" +"Click the Launchpad icon in the Dock, type \"Terminal\" in the search field, " +"then click :guilabel:`Terminal`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:83 +msgid "" +"In the Finder, open the \"/Applications/Utilities\" folder, then double-" +"click \"Terminal\"." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:85 +msgid "" +"Assuming Picard was put into the system wide Applications folder when " +"installed, it can then be started by entering the following in the terminal " +"window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:91 +#: ../../troubleshooting/troubleshooting.rst:103 +msgid "" +"This will display all log entries in the terminal window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:95 +msgid "Linux Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:97 +msgid "" +"First open a Terminal window in your desktop environment, either from the " +"Applications menu or by pressing :kbd:`Ctrl+Alt+T` on most systems. Then " +"start Picard by entering the following in the terminal window:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:59 +#: ../../troubleshooting/troubleshooting.rst:110 msgid "" "Specific situations: :doc:`does_not_start` / :doc:`no_coverart` / :doc:" "`missing_tags` / :doc:`not_saving` / :doc:`stopped_working` / :doc:" diff --git a/_locale/nl/LC_MESSAGES/troubleshooting/troubleshooting.po b/_locale/nl/LC_MESSAGES/troubleshooting/troubleshooting.po index 38d4f4810..c4dc24a56 100644 --- a/_locale/nl/LC_MESSAGES/troubleshooting/troubleshooting.po +++ b/_locale/nl/LC_MESSAGES/troubleshooting/troubleshooting.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: MusicBrainz Picard v2.7.0b2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-14 08:09+0100\n" +"POT-Creation-Date: 2023-09-22 08:57-0600\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -75,61 +75,180 @@ msgid "" "the community forums first." msgstr "" -#: ../../troubleshooting/troubleshooting.rst:28 +#: ../../troubleshooting/troubleshooting.rst:26 msgid "" "If you're still convinced you have found a new bug, open a `new ticket " "`_ providing the following information:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:31 +#: ../../troubleshooting/troubleshooting.rst:28 msgid "Which version of Picard do you use? (\"Affects Version\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:32 +#: ../../troubleshooting/troubleshooting.rst:29 msgid "Which operating system do you use? (\"Environment\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:33 +#: ../../troubleshooting/troubleshooting.rst:30 msgid "What did you do when the bug occurred?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:34 -msgid "What actually happened and what did you expect to happen?" +#: ../../troubleshooting/troubleshooting.rst:31 +msgid "What actually happened, and what did you expect to happen?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:35 +#: ../../troubleshooting/troubleshooting.rst:32 msgid "If you're using plugins, which plugins do you have enabled?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:39 -msgid ":index:`Getting Logs `" +#: ../../troubleshooting/troubleshooting.rst:33 +msgid "" +"The **\"Debug\"** level log from the Picard session demonstrating the " +"problem." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:37 +msgid "" +"Please remember to first remove any personal and confidential information " +"like user id, passwords or authorization tokens before posting or submitting " +"any log output." msgstr "" #: ../../troubleshooting/troubleshooting.rst:41 +msgid ":index:`Getting a Debug Log `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:43 msgid "" -"For many bugs, it helps developers to have a log from Picard. You can see " -"the log by going to :menuselection:`\"Help --> View Log\"`. You can also get " -"a full debug log (better because it contains more detailed information) by " -"starting Picard with :option:`-d` as a command-line argument. If you're " -"using Windows, you can change your shortcut's Target (:menuselection:`right " -"click shortcut --> Properties`) to::" +"For many bugs, it helps developers to have a debug log from Picard. You can " +"see the log by going to :menuselection:`\"Help --> View Log\"`. You can also " +"get a full debug log, which is better because it contains more detailed " +"information. Pasting this log into your forum post or bug ticket can help " +"developers and other users to resolve your issue more quickly. To retrieve " +"the full debug log:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:45 +msgid "Start Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:46 +msgid "Open the log view with :menuselection:`\"Help --> View Log\"`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:47 +msgid "Change the log level :guilabel:`verbosity` to **Debug**." msgstr "" #: ../../troubleshooting/troubleshooting.rst:48 +msgid "Close the log viewer." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:49 +msgid "Close and restart Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:50 +msgid "Repeat the action that caused the problem being reported." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:51 msgid "" -"Pasting this log into your forum post or bug ticket can help developers and " -"other users to resolve your issue more quickly." +"Open the log viewer and copy the output to paste into the forum post or bug " +"ticket. Alternately, you can save the log to a file to attach to your bug " +"report by using the :guilabel:`Save As...` button." msgstr "" #: ../../troubleshooting/troubleshooting.rst:52 +msgid "Close the log viewer, and close Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:56 msgid "" -"Please remember to first remove any personal and confidential information " -"like user id, passwords or authorization tokens before posting or submitting " -"any log output." +":index:`Getting Logs in Case of Crashes `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:58 +msgid "" +"In some cases the problem will cause Picard to crash and not allow you to " +"access the resulting log from the log viewer. You can still generate a log " +"output to attach to your report by starting Picard with the ``--debug`` " +"command line option from a command / terminal window and copying the log " +"output information from the terminal. The steps to follow for each of the " +"supported platforms are:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:61 +msgid "Windows Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:63 +msgid "" +"First open a command window by clicking the search icon on the Windows " +"Taskbar and enter \"cmd\". Then start Picard by entering the following in " +"the command window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:69 +msgid "" +"This will display all log entries in the command window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:73 +msgid "" +"This method will only work with the installed version of Picard. It will " +"not work with the portable or Windows Store versions." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:77 +msgid "macOS Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:79 +msgid "First open a terminal window by doing one of the following:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:81 +msgid "" +"Click the Launchpad icon in the Dock, type \"Terminal\" in the search field, " +"then click :guilabel:`Terminal`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:83 +msgid "" +"In the Finder, open the \"/Applications/Utilities\" folder, then double-" +"click \"Terminal\"." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:85 +msgid "" +"Assuming Picard was put into the system wide Applications folder when " +"installed, it can then be started by entering the following in the terminal " +"window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:91 +#: ../../troubleshooting/troubleshooting.rst:103 +msgid "" +"This will display all log entries in the terminal window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:95 +msgid "Linux Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:97 +msgid "" +"First open a Terminal window in your desktop environment, either from the " +"Applications menu or by pressing :kbd:`Ctrl+Alt+T` on most systems. Then " +"start Picard by entering the following in the terminal window:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:59 +#: ../../troubleshooting/troubleshooting.rst:110 msgid "" "Specific situations: :doc:`does_not_start` / :doc:`no_coverart` / :doc:" "`missing_tags` / :doc:`not_saving` / :doc:`stopped_working` / :doc:" diff --git a/_locale/pt_BR/LC_MESSAGES/troubleshooting/troubleshooting.po b/_locale/pt_BR/LC_MESSAGES/troubleshooting/troubleshooting.po index d84a5e3af..5c081cc0a 100644 --- a/_locale/pt_BR/LC_MESSAGES/troubleshooting/troubleshooting.po +++ b/_locale/pt_BR/LC_MESSAGES/troubleshooting/troubleshooting.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: MusicBrainz Picard v2.6.3\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-03-14 08:09+0100\n" +"POT-Creation-Date: 2023-09-22 08:57-0600\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -75,61 +75,180 @@ msgid "" "the community forums first." msgstr "" -#: ../../troubleshooting/troubleshooting.rst:28 +#: ../../troubleshooting/troubleshooting.rst:26 msgid "" "If you're still convinced you have found a new bug, open a `new ticket " "`_ providing the following information:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:31 +#: ../../troubleshooting/troubleshooting.rst:28 msgid "Which version of Picard do you use? (\"Affects Version\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:32 +#: ../../troubleshooting/troubleshooting.rst:29 msgid "Which operating system do you use? (\"Environment\" in the form)" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:33 +#: ../../troubleshooting/troubleshooting.rst:30 msgid "What did you do when the bug occurred?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:34 -msgid "What actually happened and what did you expect to happen?" +#: ../../troubleshooting/troubleshooting.rst:31 +msgid "What actually happened, and what did you expect to happen?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:35 +#: ../../troubleshooting/troubleshooting.rst:32 msgid "If you're using plugins, which plugins do you have enabled?" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:39 -msgid ":index:`Getting Logs `" +#: ../../troubleshooting/troubleshooting.rst:33 +msgid "" +"The **\"Debug\"** level log from the Picard session demonstrating the " +"problem." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:37 +msgid "" +"Please remember to first remove any personal and confidential information " +"like user id, passwords or authorization tokens before posting or submitting " +"any log output." msgstr "" #: ../../troubleshooting/troubleshooting.rst:41 +msgid ":index:`Getting a Debug Log `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:43 msgid "" -"For many bugs, it helps developers to have a log from Picard. You can see " -"the log by going to :menuselection:`\"Help --> View Log\"`. You can also get " -"a full debug log (better because it contains more detailed information) by " -"starting Picard with :option:`-d` as a command-line argument. If you're " -"using Windows, you can change your shortcut's Target (:menuselection:`right " -"click shortcut --> Properties`) to::" +"For many bugs, it helps developers to have a debug log from Picard. You can " +"see the log by going to :menuselection:`\"Help --> View Log\"`. You can also " +"get a full debug log, which is better because it contains more detailed " +"information. Pasting this log into your forum post or bug ticket can help " +"developers and other users to resolve your issue more quickly. To retrieve " +"the full debug log:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:45 +msgid "Start Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:46 +msgid "Open the log view with :menuselection:`\"Help --> View Log\"`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:47 +msgid "Change the log level :guilabel:`verbosity` to **Debug**." msgstr "" #: ../../troubleshooting/troubleshooting.rst:48 +msgid "Close the log viewer." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:49 +msgid "Close and restart Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:50 +msgid "Repeat the action that caused the problem being reported." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:51 msgid "" -"Pasting this log into your forum post or bug ticket can help developers and " -"other users to resolve your issue more quickly." +"Open the log viewer and copy the output to paste into the forum post or bug " +"ticket. Alternately, you can save the log to a file to attach to your bug " +"report by using the :guilabel:`Save As...` button." msgstr "" #: ../../troubleshooting/troubleshooting.rst:52 +msgid "Close the log viewer, and close Picard." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:56 msgid "" -"Please remember to first remove any personal and confidential information " -"like user id, passwords or authorization tokens before posting or submitting " -"any log output." +":index:`Getting Logs in Case of Crashes `" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:58 +msgid "" +"In some cases the problem will cause Picard to crash and not allow you to " +"access the resulting log from the log viewer. You can still generate a log " +"output to attach to your report by starting Picard with the ``--debug`` " +"command line option from a command / terminal window and copying the log " +"output information from the terminal. The steps to follow for each of the " +"supported platforms are:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:61 +msgid "Windows Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:63 +msgid "" +"First open a command window by clicking the search icon on the Windows " +"Taskbar and enter \"cmd\". Then start Picard by entering the following in " +"the command window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:69 +msgid "" +"This will display all log entries in the command window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:73 +msgid "" +"This method will only work with the installed version of Picard. It will " +"not work with the portable or Windows Store versions." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:77 +msgid "macOS Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:79 +msgid "First open a terminal window by doing one of the following:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:81 +msgid "" +"Click the Launchpad icon in the Dock, type \"Terminal\" in the search field, " +"then click :guilabel:`Terminal`." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:83 +msgid "" +"In the Finder, open the \"/Applications/Utilities\" folder, then double-" +"click \"Terminal\"." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:85 +msgid "" +"Assuming Picard was put into the system wide Applications folder when " +"installed, it can then be started by entering the following in the terminal " +"window:" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:91 +#: ../../troubleshooting/troubleshooting.rst:103 +msgid "" +"This will display all log entries in the terminal window, and allow you to " +"copy the information to the clipboard to paste into your report." +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:95 +msgid "Linux Systems" +msgstr "" + +#: ../../troubleshooting/troubleshooting.rst:97 +msgid "" +"First open a Terminal window in your desktop environment, either from the " +"Applications menu or by pressing :kbd:`Ctrl+Alt+T` on most systems. Then " +"start Picard by entering the following in the terminal window:" msgstr "" -#: ../../troubleshooting/troubleshooting.rst:59 +#: ../../troubleshooting/troubleshooting.rst:110 msgid "" "Specific situations: :doc:`does_not_start` / :doc:`no_coverart` / :doc:" "`missing_tags` / :doc:`not_saving` / :doc:`stopped_working` / :doc:"