diff --git a/docs/locales/es_ES/LC_MESSAGES/faq.po b/docs/locales/es_ES/LC_MESSAGES/faq.po index 452c33bb..3ac4cd6e 100644 --- a/docs/locales/es_ES/LC_MESSAGES/faq.po +++ b/docs/locales/es_ES/LC_MESSAGES/faq.po @@ -8,8 +8,8 @@ msgstr "" "Project-Id-Version: Pelican 4\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-01-03 17:37+0100\n" -"PO-Revision-Date: 2023-01-05 12:52+0100\n" -"Last-Translator: \n" +"PO-Revision-Date: 2023-06-24 13:23+0200\n" +"Last-Translator: Jorge Maldonado Ventura \n" "Language-Team: \n" "Language: es_ES\n" "MIME-Version: 1.0\n" @@ -33,7 +33,7 @@ msgstr "" #: ../../faq.rst:9 msgid "Please read our :doc:`feedback guidelines `." -msgstr "Por favor lee nuestras :doc:`directrices de *feedback* `." +msgstr "Por favor lee nuestras :doc:`directrices de «feedback» `." #: ../../faq.rst:12 msgid "How can I help?" @@ -54,23 +54,27 @@ msgstr "" "evitar enviar temas que hayan sido tratados anteriormente." #: ../../faq.rst:20 -#, fuzzy msgid "" "If you want to contribute, please fork `the git repository `_, create a new feature branch, make your changes, and " "issue a pull request. Someone will review your changes as soon as possible. " "Please refer to the :doc:`How to Contribute ` section for more " "details." -msgstr "Si quieres contribuir, " +msgstr "" +"Si quieres contribuir, por favor, haz un *fork* `del repositorio Git `_, crea una nueva rama para la funcionalidad, " +"haz los cambios y crea un *pull request*. Alguien revisará tus cambios tan " +"pronto como sea posible. Consulta la sección :doc:`How to Contribute " +"` para más detalles." #: ../../faq.rst:26 msgid "" "You can also contribute by creating themes and improving the documentation." -msgstr "" +msgstr "También puedes contribuir creando temas y mejorando la documentación." #: ../../faq.rst:29 msgid "Is the Pelican settings file mandatory?" -msgstr "" +msgstr "¿Es obligatorio el archivo de ajustes de Pelican?" #: ../../faq.rst:31 msgid "" @@ -78,10 +82,14 @@ msgid "" "Pelican. For basic operations, it's possible to specify options while invoking " "Pelican via the command line. See ``pelican --help`` for more information." msgstr "" +"Los archivos de configuración son opcionales y son simplemente una manera " +"sencilla de configurar Pelican. Para operaciones básicas, es posible " +"especificar opciones mientras llamas a Pelican por la línea de comandos. " +"Consulta ``pelican --help`` para más información." #: ../../faq.rst:36 msgid "Changes to the settings file take no effect" -msgstr "" +msgstr "Los cambios al archivo de configuración no hacen nada" #: ../../faq.rst:38 msgid "" @@ -90,10 +98,16 @@ msgid "" "ensure that caching is disabled via ``LOAD_CONTENT_CACHE = False`` or use the " "``--ignore-cache`` command-line switch." msgstr "" +"Al probar con diferentes ajustes (especialmente los de metadatos), el " +"almacenamiento en caché podría interferir y los cambios podrían no ser " +"visibles. En esos casos, asegúrate de que el almacenamiento en caché está " +"desactivado mediante ``LOAD_CONTENT_CACHE = False`` o usa el argumento ``--" +"ignore-cache``." #: ../../faq.rst:44 msgid "I'm creating my own theme. How do I use Pygments for syntax highlighting?" msgstr "" +"Estoy creando mi propio tema. ¿Cómo uso Pygments para el resaltado de sintaxis?" #: ../../faq.rst:46 msgid "" @@ -104,6 +118,14 @@ msgid "" "render Django code, for example, use the style selector drop-down at top-right " "on the `Pygments project demo site `_." msgstr "" +"Pygments añade algunas clases al contenido generado. Estas clases son usadas " +"por los temas para dar estilo al resaltado de sintaxis de código mediante CSS. " +"En concreto, puedes personalizar la apariencia de tu resaltado de sintaxis " +"mediante la clase ``.highlight pre`` en el archivo CSS de tu tema. Para ver " +"cómo se pueden usar estilos diferentes para representar gráficamente código de " +"Django, por ejemplo, usa el menú desplegable del selector de estilo situado en " +"la parte superior derecho del `sitio de demostración del proyecto Pygments " +"`_." #: ../../faq.rst:53 msgid "" @@ -111,18 +133,23 @@ msgid "" "from a Pygments built-in style (in this case, \"monokai\") and then copy the " "generated CSS file to your new theme::" msgstr "" +"Puedes usar los siguientes comandos de ejemplo para generar un archivo CSS " +"inicial a partir del estilo incorporado en Pygments (en este caso «monokai») y " +"luego copiar el archivo CSS generado a tu nuevo tema::" #: ../../faq.rst:60 msgid "Don't forget to import your ``pygment.css`` file from your main CSS file." msgstr "" +"No te olvides de importar tu archivo ``pygment.css`` desde tu principal " +"archivo CSS." #: ../../faq.rst:63 msgid "How do I create my own theme?" -msgstr "" +msgstr "¿Cómo creo mi propio tema?" #: ../../faq.rst:65 msgid "Please refer to :ref:`theming-pelican`." -msgstr "" +msgstr "Por favor, consulta :ref:`theming-pelican`." #: ../../faq.rst:68 msgid "I want to use Markdown, but I got an error." @@ -137,6 +164,12 @@ msgid "" "can do so by typing the following command, prepending ``sudo`` if permissions " "require it::" msgstr "" +"Si intentas generar contenido Markdown sin antes instalar la biblioteca " +"Markdown, puede que vea un mensaje que dice ``No valid files found in " +"content``. Markdown no es estrictamente una dependencia de Pelican, así que si " +"tienes contenido en formato Markdown, tendrás que instalar la biblioteca " +"Markdown. Puedes hacerlo escribiendo el siguiente comando, anteponiendo " +"``sudo`` si se requieren permisos::" #: ../../faq.rst:80 msgid "Can I use arbitrary metadata in my templates?" @@ -147,26 +180,34 @@ msgid "" "Yes. For example, to include a modified date in a Markdown post, one could " "include the following at the top of the article::" msgstr "" +"Sí. Por ejemplo, para incluir una fecha modificada en una publicación de " +"Markdown, se podría incluir lo siguiente en la parte superior del artículo::" #: ../../faq.rst:87 msgid "" "For reStructuredText, this metadata should of course be prefixed with a colon::" msgstr "" +"Por supuesto, para reStructuredText estos metadatos deben ir precedidos de dos " +"puntos::" #: ../../faq.rst:91 msgid "" "This metadata can then be accessed in templates such as ``article.html`` via::" msgstr "" +"Se puede acceder a estos metadatos en plantillas como ``article.html`` " +"mediante::" #: ../../faq.rst:97 msgid "" "If you want to include metadata in templates outside the article context (e." "g., ``base.html``), the ``if`` statement should instead be::" msgstr "" +"Si quieres incluir metadatos en plantillas fuera del contexto del artículo (p. " +"ej., ``base.html``), el código de ``ìf`` debe ser::" #: ../../faq.rst:103 msgid "How do I assign custom templates on a per-page basis?" -msgstr "" +msgstr "¿Cómo asigno plantillas personalizadas en función de la página?" #: ../../faq.rst:105 msgid "" @@ -174,36 +215,48 @@ msgid "" "you want to have its own template. For example, this is how it would be " "handled for content in reST format::" msgstr "" +"Es tan simple como añadir una línea extra de metadato a cualquier página o " +"artículo que quieras que tenga su propia plantilla. Por ejemplo, así es cómo " +"se haría para contenido en formato reST::" #: ../../faq.rst:111 msgid "For content in Markdown format::" -msgstr "" +msgstr "Para contenido en formato Markdown::" #: ../../faq.rst:115 msgid "" "Then just make sure your theme contains the relevant template file (e.g. " "``template_name.html``)." msgstr "" +"Luego simplemente asegúrate de que tu tema contiene el archivo de plantilla " +"relevante (p. ej., ``template_name.html``)." #: ../../faq.rst:119 msgid "How can I override the generated URL of a specific page or article?" msgstr "" +"¿Cómo puedo sobrescribir la URL generada para una página o artículo en " +"concreto?" #: ../../faq.rst:121 msgid "" "Include ``url`` and ``save_as`` metadata in any pages or articles that you " "want to override the generated URL. Here is an example page in reST format::" msgstr "" +"Incluye los metadatos ``url`` y ``save_as`` en las páginas o artículos en las " +"que quieras sobrescribir la URL generada. Aquí hay una página de ejemplo en " +"formato reST::" #: ../../faq.rst:130 msgid "" "With this metadata, the page will be written to ``override/url/index.html`` " "and Pelican will use url ``override/url/`` to link to this page." msgstr "" +"Con estos metadatos, la página será escrita en ``override/url/index.html`` y " +"Pelican usará la URL ``override/url/`` para enlazar a esta página." #: ../../faq.rst:134 msgid "How can I use a static page as my home page?" -msgstr "" +msgstr "¿Cómo puedo usar una página estática como mi página de inicio?" #: ../../faq.rst:136 msgid "" @@ -211,6 +264,9 @@ msgid "" "your home page. The following Markdown example could be stored in ``content/" "pages/home.md``::" msgstr "" +"La funcionalidad de sobrescritura mencionada anteriormente puede ser usada " +"para especificar una página estática como tu página de inicio. El siguiente " +"ejemplo de Markdown se podría guardar en ``content/pages/home.md``::" #: ../../faq.rst:146 msgid "" @@ -218,10 +274,13 @@ msgid "" "different location by setting ``INDEX_SAVE_AS = 'blog_index.html'`` for the " "``'index'`` direct template." msgstr "" +"Si aún quieres tener el *index* original del blog, puede guardarse en una " +"ubicación diferente asignando ``INDEX_SAVE_AS = 'blog_index.html'`` para la " +"plantilla directa ``index``." #: ../../faq.rst:151 msgid "What if I want to disable feed generation?" -msgstr "" +msgstr "¿Y si quiero desactivar la generación de fuente web?" #: ../../faq.rst:153 msgid "" @@ -229,17 +288,25 @@ msgid "" "but three feed settings already default to ``None``, so if you want to disable " "all feed generation, you only need to specify the following settings::" msgstr "" +"Para desactivar la generación de fuente web, todos los ajustes de fuente web " +"deben ponerse en ``None``. Todos los ajustes de fuente web ya están por " +"defecto en ``None``, así que si deseas desactivar toda la generación de fuente " +"web, solo tienes que especificar los siguientes ajustes::" #: ../../faq.rst:163 msgid "" "The word ``None`` should not be surrounded by quotes. Please note that " "``None`` and ``''`` are not the same thing." msgstr "" +"La palabra ``None`` no debe ser rodeada por comillas. Ten en cuenta que " +"``None`` y ``''`` no son lo mismo." #: ../../faq.rst:167 msgid "" "I'm getting a warning about feeds generated without SITEURL being set properly" msgstr "" +"Me sale una advertencia de que las fuentes web generadas sin SITEURL ajustado " +"correctamente" #: ../../faq.rst:169 msgid "" @@ -247,16 +314,25 @@ msgid "" "org/feed/docs/rss2.html#comments>`_. In order to properly generate links in " "Pelican you will need to set ``SITEURL`` to the full path of your site." msgstr "" +"`Las fuentes web de RSS y Atom requieren que todos los enlaces sean absolutos " +"`_. Para generar " +"enlaces correctamente en Pelican tendrás que poner en ``SITEURL`` la ruta " +"absoluta de tu sitio web." #: ../../faq.rst:174 msgid "" "Feeds are still generated when this warning is displayed, but links within may " "be malformed and thus the feed may not validate." msgstr "" +"Las fuentes web aún se generan cuando se muestra esta advertencia, pero los " +"enlaces en ellas podrían ser incorrectos, y, por tanto, la fuente web podría " +"no ser válida." #: ../../faq.rst:178 msgid "Can I force Atom feeds to show only summaries instead of article content?" msgstr "" +"¿Puedo hacer que las fuentes de Atom solo muestren resúmenes en vez de " +"contenido de artículos?" #: ../../faq.rst:180 msgid "" @@ -270,10 +346,21 @@ msgid "" "feed generation behavior provides users with a choice: subscribe to Atom feeds " "for full content or to RSS feeds for just the summaries." msgstr "" +"En lugar de tener que abrir una ventana separada del navegador para leer " +"artículos, la inmensa mayoría de la gente que utiliza lectores de fuentes web " +"prefiere leer el contenido dentro del propio lector de fuentes. Principalmente " +"por esa razón, Pelican no permite restringir los canales Atom para que solo " +"contengan resúmenes. A diferencia de las fuentes Atom, la especificación de " +"fuentes RSS no incluye un campo ``content`` separado, por lo que Pelican " +"publica por defecto fuentes RSS que solo contienen resúmenes (pero " +"opcionalmente se pueden configurar para publicar en su lugar fuentes RSS de " +"contenido completo). Por lo tanto, el comportamiento predeterminado de " +"generación de fuentes ofrece a los usuarios una opción: suscribirse a fuentes " +"Atom para el contenido completo o a fuentes RSS solo para los resúmenes." #: ../../faq.rst:191 msgid "Is Pelican only suitable for blogs?" -msgstr "" +msgstr "¿Pelican solo sirve para blogs?" #: ../../faq.rst:193 msgid "" @@ -283,11 +370,19 @@ msgid "" "and do not need tags on your site, you could remove the relevant HTML code " "from your theme. You can also disable generation of tag-related pages via::" msgstr "" +"No. Pelican puede configurarse fácilmente para crear y mantener cualquier tipo " +"de sitio web estático. Esto puede requerir una pequeña personalización de tu " +"tema y de tu configuración de Pelican. Por ejemplo, si estás creando un sitio " +"web de presentación para tu producto y no necesitas etiquetas en en él, " +"podrías eliminar el código HTML correspondiente de tu tema. También puedes " +"desactivar la generación de páginas asociadas a etiquetas mediante::" #: ../../faq.rst:203 msgid "" "Why does Pelican always write all HTML files even with content caching enabled?" msgstr "" +"¿Por qué Pelican escribe siempre todos los archivos HTML incluso con la caché " +"de contenido habilitada?" #: ../../faq.rst:205 msgid "" @@ -300,6 +395,15 @@ msgid "" "processing time and memory and storage space. Simply writing the files each " "time is a lot faster and a lot more reliable." msgstr "" +"Para determinar de forma fiable si la salida de HTML es diferente antes de " +"escribirla, habría que guardar y comparar una gran parte del entorno de " +"generación, incluidos los contextos de las plantillas, las extensiones " +"exportadas, etc., tendría que ser guardada y comparada, al menos en forma de " +"*hash* (lo que requeriría un manejo especial de las cosas no *hasheables*), " +"debido a todas las posibles combinaciones de extensiones, paginación, etc., " +"que podrían cambiar de muchas formas diferentes. Esto requeriría mucho más " +"tiempo de procesamiento y espacio de memoria y almacenamiento. Simplemente " +"escribir los archivos cada vez es mucho más rápido y fiable." #: ../../faq.rst:214 msgid "" @@ -309,6 +413,12 @@ msgid "" "option, which will make it compare the file checksums in a much faster way " "than Pelican would." msgstr "" +"Sin embargo, esto significa que el tiempo de modificación de los ficheros " +"cambia cada vez, por lo que una subida basada en ``rsync`` los transferirá " +"incluso si su contenido no ha cambiado. Una solución sencilla es hacer que " +"``rsync`` use la opción ``--checksum``, que hará que compare las sumas de " +"comprobación de los archivos de una forma mucho más rápida que si lo hiciera " +"Pelican." #: ../../faq.rst:220 msgid "" @@ -316,10 +426,14 @@ msgid "" "some specific page or the theme templates), the ``WRITE_SELECTED`` option may " "help, see :ref:`writing_only_selected_content`." msgstr "" +"Cuando solo son de interés algunos archivos de salida concretos (p. ej., " +"cuando se trabaja en alguna página específica o en las plantillas del tema), " +"la opción ``ẀRITE_SELECTED`` puede ser útil, consulta :ref:" +"`writing_only_selected_content`." #: ../../faq.rst:225 msgid "How to process only a subset of all articles?" -msgstr "" +msgstr "¿Cómo procesar solo un subconjunto de todos los artículos?" #: ../../faq.rst:227 msgid "" @@ -328,10 +442,15 @@ msgid "" "articles in ``ARTICLE_PATHS``. A list of such filenames could be found using a " "command similar to ``cd content; find -name '*.md' | head -n 10``." msgstr "" +"A menudo resulta útil procesar solo 10 artículos, por ejemplo, con fines de " +"depuración. Esto se puede realizar especificando explícitamente solo los " +"nombres de archivo de esos artículos en ``ARTICLE_PATHS``. Se podría obtener " +"una lista de esos nombres de archivo usando un comando como ``cd content; find " +"-name '*.md' | head -n 10``." #: ../../faq.rst:233 msgid "My tag-cloud is missing/broken since I upgraded Pelican" -msgstr "" +msgstr "Desde que actualicé Pelican falta/está rota mi nube de etiquetas" #: ../../faq.rst:235 msgid "" @@ -340,10 +459,15 @@ msgid "" "pelican-plugins/tag-cloud>`_. See the :ref:`plugins` documentation for further " "information about the Pelican plugin system." msgstr "" +"En un esfuerzo continuo por optimizar Pelican, la generación de la nube de " +"etiquetas se ha trasladado del núcleo de Pelican a un `complemento `_ separado. Consulta la documentación " +"de :ref:`plugins` para más información sobre el sistema de complementos de " +"Pelican." #: ../../faq.rst:241 msgid "Since I upgraded Pelican my pages are no longer rendered" -msgstr "" +msgstr "Desde que actualicé Pelican mis páginas no se procesan" #: ../../faq.rst:243 msgid "" @@ -352,14 +476,20 @@ msgid "" "has been removed. This is quickly resolved by updating your theme to iterate " "over ``pages`` instead of ``PAGES``. Just replace::" msgstr "" +"Las páginas estaban disponibles en los temas como ``pages`` (en minúscula) y " +"``PAGES`` (en mayúscula). Para ajustar esto a la sección :ref:`templates-" +"variables`, se eliminó ``PAGES``. Esto se arregla fácilmente actualizando tu " +"tema para iterar en ``pages`` en vez de en ``PAGES``. Simplemente reemplaza::" #: ../../faq.rst:250 msgid "with something like::" -msgstr "" +msgstr "por algo como::" #: ../../faq.rst:255 msgid "How can I stop Pelican from trying to parse my static files as content?" msgstr "" +"¿Cómo puedo evitar que Pelican intente procesar mis archivos estáticos como " +"contenido?" #: ../../faq.rst:257 msgid "" @@ -369,16 +499,24 @@ msgid "" "a valid content file ending (``.html``, ``.rst``, ``.md``, ...) will be " "treated as articles or pages before they get treated as static files." msgstr "" +"Los generadores de artículos y páginas de Pelican se ejecutan antes que el " +"generador estático. Esto significa que si usas una configuración similar a la " +"predeterminada, en la que se define un directorio fuente estático dentro de un " +"ajuste ``*_PATHS``, todos los archivos que tengan una extensión de archivo " +"válida (``.html``, ``.rst``, ``.md``, ...) serán tratados como artículos o " +"páginas antes de ser tratados como archivos estáticos." #: ../../faq.rst:263 msgid "" "To circumvent this issue either use the appropriate ``*_EXCLUDES`` setting or " "disable the offending reader via ``READERS`` if you don't need it." msgstr "" +"Para evitar este problema, utiliza la configuración ``*_EXCLUDES`` adecuada o " +"desactiva el lector problemático mediante ``READERS`` si no lo necesitas." #: ../../faq.rst:267 msgid "Why is [arbitrary Markdown syntax] not supported?" -msgstr "" +msgstr "¿Por qué no está soportado [sintaxis de Markdown x]?" #: ../../faq.rst:269 msgid "" @@ -392,3 +530,13 @@ msgid "" "best choice if there is a particular variant you want to use when writing your " "content." msgstr "" +"Pelican no maneja directamente el procesamiento de Markdown y en su lugar " +"delega esa tarea al proyecto Python-Markdown_, cuyo núcleo sigue " +"deliberadamente las reglas sintácticas originales de Markdown y no la miríada " +"de «sabores» de Markdown que se han extendido posteriormente. Dicho esto, " +"Python-Markdown_ es bastante modular, y la sintaxis que estás buscando puede " +"ser proporcionada por una de las muchas `Extensiones de Markdown`_ " +"disponibles. Alternativamente, algunas personas han creado extensiones de " +"Pelican que soportan variantes de Markdown, así que esto podría ser tu mejor " +"opción si hay una variante particular que deseas utilizar al escribir tu " +"contenido." diff --git a/docs/locales/es_ES/LC_MESSAGES/index.po b/docs/locales/es_ES/LC_MESSAGES/index.po index 5f04df5f..aee7016b 100644 --- a/docs/locales/es_ES/LC_MESSAGES/index.po +++ b/docs/locales/es_ES/LC_MESSAGES/index.po @@ -8,8 +8,8 @@ msgstr "" "Project-Id-Version: Pelican 4\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-01-03 17:37+0100\n" -"PO-Revision-Date: 2023-01-03 18:09+0100\n" -"Last-Translator: \n" +"PO-Revision-Date: 2023-06-24 12:21+0200\n" +"Last-Translator: Jorge Maldonado Ventura \n" "Language-Team: \n" "Language: es_ES\n" "MIME-Version: 1.0\n" @@ -55,7 +55,7 @@ msgstr "" msgid "Ready to get started? Check out the :doc:`Quickstart` guide." msgstr "" "¿Listo para comenzar? Echa un vistazo a la guía :doc:`Comienzo " -"rápido`" +"rápido`." #: ../../index.rst:24 msgid "Features" diff --git a/docs/locales/es_ES/LC_MESSAGES/plugins.po b/docs/locales/es_ES/LC_MESSAGES/plugins.po index 731fe01f..1a117ba6 100644 --- a/docs/locales/es_ES/LC_MESSAGES/plugins.po +++ b/docs/locales/es_ES/LC_MESSAGES/plugins.po @@ -3,29 +3,29 @@ # This file is distributed under the same license as the Pelican package. # FIRST AUTHOR , 2023. # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: Pelican 4\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-01-03 17:37+0100\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" +"PO-Revision-Date: 2023-06-24 13:07+0200\n" +"Last-Translator: Jorge Maldonado Ventura \n" +"Language-Team: \n" +"Language: es_ES\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.11.0\n" +"X-Generator: Poedit 3.2.2\n" #: ../../plugins.rst:4 msgid "Plugins" -msgstr "" +msgstr "Complementos" #: ../../plugins.rst:6 msgid "" -"Beginning with version 3.0, Pelican supports plugins. Plugins are a way " -"to add features to Pelican without having to directly modify the Pelican " -"core." +"Beginning with version 3.0, Pelican supports plugins. Plugins are a way to " +"add features to Pelican without having to directly modify the Pelican core." msgstr "" #: ../../plugins.rst:10 @@ -34,30 +34,28 @@ msgstr "" #: ../../plugins.rst:12 msgid "" -"Starting with version 4.5, Pelican moved to a new plugin structure " -"utilizing namespace packages that can be easily installed via Pip_. " -"Plugins supporting this structure will install under the namespace " -"package ``pelican.plugins`` and can be automatically discovered by " -"Pelican. To see a list of Pip-installed namespace plugins that are active" -" in your environment, run::" +"Starting with version 4.5, Pelican moved to a new plugin structure utilizing " +"namespace packages that can be easily installed via Pip_. Plugins supporting " +"this structure will install under the namespace package ``pelican.plugins`` " +"and can be automatically discovered by Pelican. To see a list of Pip-" +"installed namespace plugins that are active in your environment, run::" msgstr "" #: ../../plugins.rst:20 msgid "" "If you leave the ``PLUGINS`` setting as default (``None``), Pelican will " -"automatically discover namespace plugins and register them. If, on the " -"other hand, you specify a ``PLUGINS`` setting as a list of plugins, this " -"auto-discovery will be disabled. At that point, only the plugins you " -"specify will be registered, and you must explicitly list any namespace " -"plugins as well." +"automatically discover namespace plugins and register them. If, on the other " +"hand, you specify a ``PLUGINS`` setting as a list of plugins, this auto-" +"discovery will be disabled. At that point, only the plugins you specify will " +"be registered, and you must explicitly list any namespace plugins as well." msgstr "" #: ../../plugins.rst:26 msgid "" "If you are using the ``PLUGINS`` setting, you can specify plugins in two " "ways. The first method specifies plugins as a list of strings. Namespace " -"plugins can be specified either by their full names " -"(``pelican.plugins.myplugin``) or by their short names (``myplugin``)::" +"plugins can be specified either by their full names (``pelican.plugins." +"myplugin``) or by their short names (``myplugin``)::" msgstr "" #: ../../plugins.rst:35 @@ -69,17 +67,17 @@ msgstr "" #: ../../plugins.rst:43 msgid "" "When experimenting with different plugins (especially the ones that deal " -"with metadata and content) caching may interfere and the changes may not " -"be visible. In such cases disable caching with ``LOAD_CONTENT_CACHE = " -"False`` or use the ``--ignore-cache`` command-line switch." +"with metadata and content) caching may interfere and the changes may not be " +"visible. In such cases disable caching with ``LOAD_CONTENT_CACHE = False`` " +"or use the ``--ignore-cache`` command-line switch." msgstr "" #: ../../plugins.rst:48 msgid "" "If your plugins are not in an importable path, you can specify a list of " -"paths via the ``PLUGIN_PATHS`` setting. As shown in the following " -"example, paths in the ``PLUGIN_PATHS`` list can be absolute or relative " -"to the settings file::" +"paths via the ``PLUGIN_PATHS`` setting. As shown in the following example, " +"paths in the ``PLUGIN_PATHS`` list can be absolute or relative to the " +"settings file::" msgstr "" #: ../../plugins.rst:56 @@ -89,16 +87,16 @@ msgstr "" #: ../../plugins.rst:57 msgid "" "Namespace plugins can be found in the `pelican-plugins organization`_ as " -"individual repositories. Legacy plugins are located in the `pelican-" -"plugins repository`_ and will be gradually phased out in favor of the " -"namespace versions." +"individual repositories. Legacy plugins are located in the `pelican-plugins " +"repository`_ and will be gradually phased out in favor of the namespace " +"versions." msgstr "" #: ../../plugins.rst:65 msgid "" -"Please note that while we do our best to review and maintain these " -"plugins, they are submitted by the Pelican community and thus may have " -"varying levels of support and interoperability." +"Please note that while we do our best to review and maintain these plugins, " +"they are submitted by the Pelican community and thus may have varying levels " +"of support and interoperability." msgstr "" #: ../../plugins.rst:70 @@ -114,24 +112,22 @@ msgstr "" #: ../../plugins.rst:76 msgid "" -"The only rule to follow for plugins is to define a ``register`` callable," -" in which you map the signals to your plugin logic. Let's take a simple " -"example::" +"The only rule to follow for plugins is to define a ``register`` callable, in " +"which you map the signals to your plugin logic. Let's take a simple example::" msgstr "" #: ../../plugins.rst:93 msgid "" -"Signal receivers are weakly-referenced and thus must not be defined " -"within your ``register`` callable or they will be garbage-collected " -"before the signal is emitted." +"Signal receivers are weakly-referenced and thus must not be defined within " +"your ``register`` callable or they will be garbage-collected before the " +"signal is emitted." msgstr "" #: ../../plugins.rst:97 msgid "" -"If multiple plugins connect to the same signal, there is no way to " -"guarantee or control in which order the plugins will be executed. This is" -" a limitation inherited from Blinker_, the dependency Pelican uses to " -"implement signals." +"If multiple plugins connect to the same signal, there is no way to guarantee " +"or control in which order the plugins will be executed. This is a limitation " +"inherited from Blinker_, the dependency Pelican uses to implement signals." msgstr "" #: ../../plugins.rst:102 @@ -140,25 +136,25 @@ msgstr "" #: ../../plugins.rst:104 msgid "" -"Namespace plugins must adhere to a certain structure in order to function" -" properly. They need to be installable (i.e. contain ``setup.py`` or " +"Namespace plugins must adhere to a certain structure in order to function " +"properly. They need to be installable (i.e. contain ``setup.py`` or " "equivalent) and have a folder structure as follows::" msgstr "" #: ../../plugins.rst:117 msgid "" -"It is crucial that ``pelican`` or ``pelican/plugins`` folder **not** " -"contain an ``__init__.py`` file. In fact, it is best to have those " -"folders empty besides the listed folders in the above structure and keep " -"your plugin related files contained solely in the " -"``pelican/plugins/myplugin`` folder to avoid any issues." +"It is crucial that ``pelican`` or ``pelican/plugins`` folder **not** contain " +"an ``__init__.py`` file. In fact, it is best to have those folders empty " +"besides the listed folders in the above structure and keep your plugin " +"related files contained solely in the ``pelican/plugins/myplugin`` folder to " +"avoid any issues." msgstr "" #: ../../plugins.rst:123 msgid "" "To easily set up the proper structure, a `cookiecutter template for " -"plugins`_ is provided. Refer to that project's README for instructions on" -" how to use it." +"plugins`_ is provided. Refer to that project's README for instructions on " +"how to use it." msgstr "" #: ../../plugins.rst:129 @@ -196,9 +192,9 @@ msgstr "" #: ../../plugins.rst:137 msgid "" -"invoked after all the generators are executed and just before pelican " -"exits useful for custom post processing actions, such as: - minifying " -"js/css assets. - notify/ping search engines with an updated sitemap." +"invoked after all the generators are executed and just before pelican exits " +"useful for custom post processing actions, such as: - minifying js/css " +"assets. - notify/ping search engines with an updated sitemap." msgstr "" #: ../../plugins.rst:141 @@ -256,8 +252,8 @@ msgstr "" #: ../../plugins.rst:145 msgid "" -"invoked before a article is read in ArticlesGenerator.generate_context; " -"use if code needs to do something before every article is parsed" +"invoked before a article is read in ArticlesGenerator.generate_context; use " +"if code needs to do something before every article is parsed" msgstr "" #: ../../plugins.rst:147 @@ -275,8 +271,8 @@ msgstr "" #: ../../plugins.rst:148 msgid "" "invoked before categories and tags lists are created useful when e.g. " -"modifying the list of articles to be generated so that removed articles " -"are not leaked in categories or tags" +"modifying the list of articles to be generated so that removed articles are " +"not leaked in categories or tags" msgstr "" #: ../../plugins.rst:151 ../../plugins.rst:199 @@ -309,8 +305,8 @@ msgstr "" #: ../../plugins.rst:153 msgid "" -"invoked after all articles and related pages have been written, but " -"before the article generator is closed." +"invoked after all articles and related pages have been written, but before " +"the article generator is closed." msgstr "" #: ../../plugins.rst:155 @@ -319,8 +315,8 @@ msgstr "" #: ../../plugins.rst:155 msgid "" -"invoked in Pelican.get_generator_classes, can return a Generator, or " -"several generators in a tuple or in a list." +"invoked in Pelican.get_generator_classes, can return a Generator, or several " +"generators in a tuple or in a list." msgstr "" #: ../../plugins.rst:158 @@ -349,8 +345,8 @@ msgstr "" #: ../../plugins.rst:161 msgid "" -"invoked before a page is read in PageGenerator.generate_context; use if " -"code needs to do something before every page is parsed." +"invoked before a page is read in PageGenerator.generate_context; use if code " +"needs to do something before every page is parsed." msgstr "" #: ../../plugins.rst:163 ../../plugins.rst:204 @@ -391,8 +387,8 @@ msgstr "" #: ../../plugins.rst:166 msgid "" -"invoked after all pages have been written, but before the page generator " -"is closed." +"invoked after all pages have been written, but before the page generator is " +"closed." msgstr "" #: ../../plugins.rst:168 ../../plugins.rst:205 @@ -413,9 +409,9 @@ msgstr "" #: ../../plugins.rst:169 msgid "" -"invoked before a static file is read in StaticGenerator.generate_context;" -" use if code needs to do something before every static file is added to " -"the staticfiles list." +"invoked before a static file is read in StaticGenerator.generate_context; " +"use if code needs to do something before every static file is added to the " +"staticfiles list." msgstr "" #: ../../plugins.rst:172 @@ -468,8 +464,8 @@ msgstr "" #: ../../plugins.rst:176 msgid "" -"invoked each time a feed gets generated. Can be used to modify a feed " -"object before it gets written." +"invoked each time a feed gets generated. Can be used to modify a feed object " +"before it gets written." msgstr "" #: ../../plugins.rst:178 @@ -486,18 +482,18 @@ msgstr "" #: ../../plugins.rst:183 msgid "" -"Avoid ``content_object_init`` signal if you intend to read ``summary`` or" -" ``content`` properties of the content object. That combination can " -"result in unresolved links when :ref:`ref-linking-to-internal-content` " -"(see `pelican-plugins bug #314`_). Use ``_summary`` and ``_content`` " -"properties instead, or, alternatively, run your plugin at a later stage " -"(e.g. ``all_generators_finalized``)." +"Avoid ``content_object_init`` signal if you intend to read ``summary`` or " +"``content`` properties of the content object. That combination can result in " +"unresolved links when :ref:`ref-linking-to-internal-content` (see `pelican-" +"plugins bug #314`_). Use ``_summary`` and ``_content`` properties instead, " +"or, alternatively, run your plugin at a later stage (e.g. " +"``all_generators_finalized``)." msgstr "" #: ../../plugins.rst:192 msgid "" -"After Pelican 3.2, signal names were standardized. Older plugins may " -"need to be updated to use the new names:" +"After Pelican 3.2, signal names were standardized. Older plugins may need " +"to be updated to use the new names:" msgstr "" #: ../../plugins.rst:196 @@ -550,8 +546,8 @@ msgstr "" #: ../../plugins.rst:212 msgid "" -"We eventually realised some of the recipes to create plugins would be " -"best shared in the documentation somewhere, so here they are!" +"We eventually realised some of the recipes to create plugins would be best " +"shared in the documentation somewhere, so here they are!" msgstr "" #: ../../plugins.rst:216 @@ -560,16 +556,16 @@ msgstr "" #: ../../plugins.rst:218 msgid "" -"One thing you might want is to add support for your very own input " -"format. While it might make sense to add this feature in Pelican core, we" -" wisely chose to avoid this situation and instead have the different " -"readers defined via plugins." +"One thing you might want is to add support for your very own input format. " +"While it might make sense to add this feature in Pelican core, we wisely " +"chose to avoid this situation and instead have the different readers defined " +"via plugins." msgstr "" #: ../../plugins.rst:223 msgid "" -"The rationale behind this choice is mainly that plugins are really easy " -"to write and don't slow down Pelican itself when they're not active." +"The rationale behind this choice is mainly that plugins are really easy to " +"write and don't slow down Pelican itself when they're not active." msgstr "" #: ../../plugins.rst:226 @@ -582,9 +578,8 @@ msgstr "" #: ../../plugins.rst:264 msgid "" -"Adding a new generator is also really easy. You might want to have a look" -" at :doc:`internals` for more information on how to create your own " -"generator." +"Adding a new generator is also really easy. You might want to have a look " +"at :doc:`internals` for more information on how to create your own generator." msgstr "" #: ../../plugins.rst:278 @@ -593,10 +588,10 @@ msgstr "" #: ../../plugins.rst:280 msgid "" -"Adding a writer will allow you to output additional file formats to disk," -" or change how the existing formats are written to disk. Note that only " -"one writer will be active at a time, so be sure to either subclass the " -"built-in Writer, or completely re-implement it." +"Adding a writer will allow you to output additional file formats to disk, or " +"change how the existing formats are written to disk. Note that only one " +"writer will be active at a time, so be sure to either subclass the built-in " +"Writer, or completely re-implement it." msgstr "" #: ../../plugins.rst:285 @@ -609,13 +604,12 @@ msgstr "" #: ../../plugins.rst:307 msgid "" -"You can programmatically inject articles or pages using plugins. This can" -" be useful if you plan to fetch articles from an API, for example." +"You can programmatically inject articles or pages using plugins. This can be " +"useful if you plan to fetch articles from an API, for example." msgstr "" #: ../../plugins.rst:310 msgid "" -"Following is a simple example of how one can build a plugin that injects " -"a custom article, using the ``article_generator_pretaxonomy`` signal::" +"Following is a simple example of how one can build a plugin that injects a " +"custom article, using the ``article_generator_pretaxonomy`` signal::" msgstr "" -