Added translation using Weblate (Lithuanian)

Added translation using Weblate (Lithuanian) Added translation using Weblate (Lithuanian) Co-authored-by: Languages add-on <[email protected]>
metabrainz · Jan 31, 2025 · 01c3c48 · 01c3c48
1 parent d395630
commit 01c3c48
Show file tree

Hide file tree

Showing 3 changed files with 333 additions and 0 deletions.
diff --git a/_locale/lt/LC_MESSAGES/functions/func_slice.po b/_locale/lt/LC_MESSAGES/functions/func_slice.po
@@ -0,0 +1,56 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) This documentation is licensed under CC0 1.0.
+# This file is distributed under the same license as the MusicBrainz Picard package.
+# Languages add-on <[email protected]>, 2025.
+msgid ""
+msgstr ""
+"Project-Id-Version: MusicBrainz Picard v2.11.0rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-01-11 23:26+0100\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: lt\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../functions/func_slice.rst:6
+msgid "$slice"
+msgstr ""
+
+#: ../../functions/func_slice.rst:8
+msgid "Usage: **$slice(name,start[,end[,separator]])**"
+msgstr ""
+
+#: ../../functions/func_slice.rst:9
+msgid "Category: multi-value"
+msgstr ""
+
+#: ../../functions/func_slice.rst:10
+msgid "Implemented: Picard 2.3"
+msgstr ""
+
+#: ../../functions/func_slice.rst:12
+msgid "**Description:**"
+msgstr ""
+
+#: ../../functions/func_slice.rst:14
+msgid "Returns a multi-value variable containing the elements from the ``start`` index up to but not including the ``end`` index from the multi-value variable ``name``. A literal value representing a multi-value can be substituted for ``name``, using the ``separator`` (or a semicolon followed by a space \"; \" if not passed) to coerce the value into a proper multi-valued variable."
+msgstr ""
+
+#: ../../functions/func_slice.rst:20
+msgid "Indexes are zero based. Negative numbers will be counted back from the number of elements in the list. If the ``start`` or ``end`` indexes are left blank, they will default to 0 and the number of elements in the list respectively."
+msgstr ""
+
+#: ../../functions/func_slice.rst:24
+msgid "A typical use might be to create a multi-value variable with all artists in ``%artists%`` except the first, which can be used to create a \"feat.\" list.  This would look something like ``$setmulti(supporting_artists,$slice(%artists%,1))``."
+msgstr ""
+
+#: ../../functions/func_slice.rst:29
+msgid "**Example:**"
+msgstr ""
+
+#: ../../functions/func_slice.rst:31
+msgid "The following statements will return the values indicated:"
+msgstr ""
diff --git a/_locale/lt/LC_MESSAGES/troubleshooting/no_coverart.po b/_locale/lt/LC_MESSAGES/troubleshooting/no_coverart.po
@@ -0,0 +1,88 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) This documentation is licensed under CC0 1.0.
+# This file is distributed under the same license as the MusicBrainz Picard package.
+# Languages add-on <[email protected]>, 2025.
+msgid ""
+msgstr ""
+"Project-Id-Version: MusicBrainz Picard v2.11.0rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-01-11 23:26+0100\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: lt\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../troubleshooting/no_coverart.rst:8
+msgid "There is no coverart"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:10
+msgid "There are two different problems that often fall under this topic:"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:13
+msgid ":index:`Picard isn't finding and downloading any cover art <troubleshooting; no cover art downloaded>`"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:15
+msgid "**No cover art providers have been enabled in the configuration settings**"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:17
+msgid "Confirm that the :menuselection:`\"Options --> Options... --> Cover Art\"` settings have at least one cover art provider enabled.  Please see the :doc:`/config/options_cover_art_providers` section for more information."
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:20
+msgid "**There is no cover art available from the selected providers**"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:22
+msgid "It's possible that the selected release does not have any cover art available from the enabled cover art providers. If a cover art image is displayed for the release on the MusicBrainz website, it is possible that the image for the release group is being displayed, or it is being provided through a third-party provider agreement.  Sometimes this can be addressed by enabling the \"CAA Release Group\" and \"Allowed cover art URLs\" provider options."
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:28
+msgid "**The selected provider is not currently available**"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:30
+msgid "On occasion, the server providing the cover art (e.g.: archive.org) is not available, or mirror servers have not yet been synchronized with the latest updates.  In this case, you may have to wait for a few minutes before retrying your request. Reviewing the details in Picard's log often provides some insight into whether or not this is the issue."
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:35
+msgid "**The cover art is still a pending edit**"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:37
+msgid "If the cover art was recently added, the edit adding the image may not have been accepted and applied yet. You can have Picard use the cover art from pending edits by disabling the \"Download only approved images\" option in the Cover Art Archives subsection of the :menuselection:`\"Options --> Options... --> Cover Art\"` settings.  Please see the :doc:`/config/options_cover_art_archive` section for more information."
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:44
+msgid ":index:`Coverart that is saved with the files isn't displayed <troubleshooting; no cover art displayed>`"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:46
+msgid "**Player doesn't support embedded cover art**"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:48
+msgid "Check to confirm that your player supports embedded cover art images.  That support is not universal among all players.  Some players support embedded images, some support images stored as files in the directory (e.g.: :file:`cover.jpg` or :file:`folder.jpg`), and some support both. Picard allows you to specify how the cover art images should be saved.  Please see the :doc:`/config/options_location` section of the Coverart options for details."
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:53
+msgid "You should also confirm that your player supports the version of the tags being written."
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:57
+msgid "For more information please see: :doc:`/config/options_tags_compatibility_aac` / :doc:`/config/options_tags_compatibility_ac3` / :doc:`/config/options_tags_compatibility_id3` / :doc:`/config/options_tags_compatibility_wave`"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:63
+msgid "**Embedded cover image too large**"
+msgstr ""
+
+#: ../../troubleshooting/no_coverart.rst:65
+msgid "Even if your cover art image has been properly embedded in the file, it's possible that your player has trouble dealing with embedded images over a certain size.  If all else fails, you might try using an image with a smaller file size."
+msgstr ""
diff --git a/_locale/lt/LC_MESSAGES/troubleshooting/troubleshooting.po b/_locale/lt/LC_MESSAGES/troubleshooting/troubleshooting.po
@@ -0,0 +1,189 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) This documentation is licensed under CC0 1.0.
+# This file is distributed under the same license as the MusicBrainz Picard package.
+# Languages add-on <[email protected]>, 2025.
+msgid ""
+msgstr ""
+"Project-Id-Version: MusicBrainz Picard v3.0rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-01-31 09:30-0700\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"Language: lt\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../troubleshooting/troubleshooting.rst:4
+msgid ":index:`General Troubleshooting <troubleshooting; general>`"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:7
+msgid "Getting Help"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:9
+msgid "If you have problems using Picard, please first check the following resources:"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:11
+msgid "For general usage information see the :doc:`/usage/using` documentation and the `illustrated quick start guide <https://picard.musicbrainz.org/quick-start/>`_."
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:13
+msgid "Read the :doc:`FAQ section </faq/faq>` for common questions and problems."
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:14
+msgid "Consult the `community forums <https://community.metabrainz.org/c/picard>`_."
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:15
+msgid "Check the `download page <https://picard.musicbrainz.org/downloads/>`_ for a newer version of Picard which might solve your problem."
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:17
+msgid "If the problem is to do with a plugin, check the `Picard Plugins <https://picard.musicbrainz.org/plugins/>`_ for updated plugin versions."
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:22
+msgid ":index:`Reporting a Bug <troubleshooting; reporting a bug>`"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:24
+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 <https://tickets.musicbrainz.org/browse/PICARD>`_. 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:26
+msgid "If you're still convinced you have found a new bug, open a `new ticket <https://tickets.musicbrainz.org/secure/CreateIssue.jspa?pid=10042&issuetype=1>`_ providing the following information:"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:28
+msgid "Which version of Picard do you use? (\"Affects Version\" in the form)"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:29
+msgid "Which operating system do you use? (\"Environment\" in the form)"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:30
+msgid "What did you do when the bug occurred?"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:31
+msgid "What actually happened, and what did you expect to happen?"
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:32
+msgid "If you're using plugins, which plugins do you have enabled?"
+msgstr ""
+
+#: ../../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 <troubleshooting; get 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 "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 "Close the log viewer, and close Picard."
+msgstr ""
+
+#: ../../troubleshooting/troubleshooting.rst:56
+msgid ":index:`Getting Logs in Case of Crashes <troubleshooting; getting log for 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:110
+msgid "Specific situations: :doc:`/troubleshooting/does_not_start` / :doc:`/troubleshooting/no_coverart` / :doc:`/troubleshooting/missing_tags` / :doc:`/troubleshooting/not_saving` / :doc:`/troubleshooting/stopped_working` / :doc:`/troubleshooting/macos_startup_error`"
+msgstr ""