mirror of
https://github.com/getpelican/pelican.git
synced 2025-10-15 20:28:56 +02:00
Avanza
This commit is contained in:
Jorge Maldonado Ventura
parent
d1c5aea4a5
commit
cb0d741e2a
4 changed files with 372 additions and 263 deletions
|
|
@ -8,7 +8,7 @@ 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 17:53+0100\n"
|
||||
"PO-Revision-Date: 2023-01-30 10:03+0100\n"
|
||||
"Last-Translator: \n"
|
||||
"Language-Team: \n"
|
||||
"Language: es_ES\n"
|
||||
|
|
@ -47,10 +47,11 @@ msgstr ""
|
|||
#: ../../content.rst:14
|
||||
msgid "You can find sample content in the repository at ``samples/content/``."
|
||||
msgstr ""
|
||||
"Puedes encontrar contenido de muestra en el repositorio en ``samples/content/``."
|
||||
|
||||
#: ../../content.rst:19
|
||||
msgid "File metadata"
|
||||
msgstr ""
|
||||
msgstr "Metadatos de archivo"
|
||||
|
||||
#: ../../content.rst:21
|
||||
msgid ""
|
||||
|
|
@ -58,6 +59,10 @@ msgid ""
|
|||
"system (for instance, about the category of your articles), but some "
|
||||
"information you need to provide in the form of metadata inside your files."
|
||||
msgstr ""
|
||||
"Pelican trata de ser lo suficientemente inteligente para obtener la información "
|
||||
"que necesita del sistema de archivos (por ejemplo, sobre la categoría de tus "
|
||||
"artículos), pero necesitas proporcionar alguna información en forma de "
|
||||
"metadatos dentro de tus archivos."
|
||||
|
||||
#: ../../content.rst:25
|
||||
msgid ""
|
||||
|
|
@ -65,18 +70,27 @@ msgid ""
|
|||
"this metadata in text files via the following syntax (give your file the ``."
|
||||
"rst`` extension)::"
|
||||
msgstr ""
|
||||
"Si estás escribiendo tu contenido en formato reStructuredText, puedes "
|
||||
"proporcionar estos metadatos en archivos de texto mediante la siguiente "
|
||||
"sintaxis (dale a tu archivo la extensión ``.rst``)::"
|
||||
|
||||
#: ../../content.rst:40
|
||||
msgid ""
|
||||
"Author and tag lists may be semicolon-separated instead, which allows you to "
|
||||
"write authors and tags containing commas::"
|
||||
msgstr ""
|
||||
"Las listas de autor y de etiqueta también pueden separarse en su lugar por "
|
||||
"puntos y coma, lo que te permite escribir autores y etiquetas que contienen "
|
||||
"comas::"
|
||||
|
||||
#: ../../content.rst:46
|
||||
msgid ""
|
||||
"Pelican implements an extension to reStructuredText to enable support for the "
|
||||
"``abbr`` HTML tag. To use it, write something like this in your post::"
|
||||
msgstr ""
|
||||
"Pelican implementa una extensión para reStructuredText para permitir soportar "
|
||||
"la etiqueta HTML ``abbr``. Para usarla escribe algo como esto en tu "
|
||||
"publicación::"
|
||||
|
||||
#: ../../content.rst:51
|
||||
msgid ""
|
||||
|
|
@ -85,6 +99,10 @@ msgid ""
|
|||
"explicitly install the Python-Markdown_ package, which can be done via ``pip "
|
||||
"install Markdown``."
|
||||
msgstr ""
|
||||
"También puedes usar la sintaxis de Markdown (con un archivo acabado en ``.md``, "
|
||||
"``.markdown``, ``.mkd`` o ``.mdown``). La generación de Markdown requiere que "
|
||||
"primero instales explícitamente el paquete Python-Markdown_, lo cual se puede "
|
||||
"hacer mediante ``pip install Markdown``."
|
||||
|
||||
#: ../../content.rst:56
|
||||
msgid ""
|
||||
|
|
@ -92,10 +110,14 @@ msgid ""
|
|||
"separately if they are not included in the default ``Markdown`` package and can "
|
||||
"be configured and loaded via the ``MARKDOWN`` setting."
|
||||
msgstr ""
|
||||
"Pelican también soporta `Markdown Extensions`_, que puede que tenga que ser "
|
||||
"instalado de forma separada si no se incluyen en el paquete ``Markdown`` "
|
||||
"predeterminado y pueden ser configuradas y cargadas mediante el ajuste "
|
||||
"``MARKDOWN``."
|
||||
|
||||
#: ../../content.rst:60
|
||||
msgid "Metadata syntax for Markdown posts should follow this pattern::"
|
||||
msgstr ""
|
||||
msgstr "La sintaxis de metadatos para publicaciones Markdown sigue este patrón::"
|
||||
|
||||
#: ../../content.rst:73
|
||||
msgid ""
|
||||
|
|
@ -103,148 +125,156 @@ msgid ""
|
|||
"reserved metadata keywords) for use in your templates. The following table "
|
||||
"contains a list of reserved metadata keywords:"
|
||||
msgstr ""
|
||||
"También puedes tener tus propias claves de metadatos (siempre que no entren en "
|
||||
"conflicto con las palabras clave reservadas de metadatos) para usarlas en tus "
|
||||
"plantillas. La siguiente tabla contiene una lista de palabras clave de "
|
||||
"metadatos reservadas:"
|
||||
|
||||
#: ../../content.rst:78
|
||||
msgid "Metadata"
|
||||
msgstr ""
|
||||
msgstr "Metadatos"
|
||||
|
||||
#: ../../content.rst:78 ../../content.rst:544
|
||||
msgid "Description"
|
||||
msgstr ""
|
||||
msgstr "Descripción"
|
||||
|
||||
#: ../../content.rst:80
|
||||
msgid "``title``"
|
||||
msgstr ""
|
||||
msgstr "``title``"
|
||||
|
||||
#: ../../content.rst:80
|
||||
msgid "Title of the article or page"
|
||||
msgstr ""
|
||||
msgstr "Título del artículo o página"
|
||||
|
||||
#: ../../content.rst:81
|
||||
msgid "``date``"
|
||||
msgstr ""
|
||||
msgstr "``date``"
|
||||
|
||||
#: ../../content.rst:81
|
||||
msgid "Publication date (e.g., ``YYYY-MM-DD HH:SS``)"
|
||||
msgstr ""
|
||||
msgstr "Fecha de publicación (p. ej., ``AAAA-MM-DD HH:SS``)"
|
||||
|
||||
#: ../../content.rst:82
|
||||
msgid "``modified``"
|
||||
msgstr ""
|
||||
msgstr "``modified``"
|
||||
|
||||
#: ../../content.rst:82
|
||||
msgid "Modification date (e.g., ``YYYY-MM-DD HH:SS``)"
|
||||
msgstr ""
|
||||
msgstr "Fecha de modificación (p. ej., ``AAAA-MM-DD HH:SS``)"
|
||||
|
||||
#: ../../content.rst:83
|
||||
msgid "``tags``"
|
||||
msgstr ""
|
||||
msgstr "``tags``"
|
||||
|
||||
#: ../../content.rst:83
|
||||
msgid "Content tags, separated by commas"
|
||||
msgstr ""
|
||||
msgstr "Etiquetas de contenido, separadas por comas"
|
||||
|
||||
#: ../../content.rst:84
|
||||
msgid "``keywords``"
|
||||
msgstr ""
|
||||
msgstr "``keywords``"
|
||||
|
||||
#: ../../content.rst:84
|
||||
msgid "Content keywords, separated by commas (HTML content only)"
|
||||
msgstr ""
|
||||
msgstr "Palabras claves del contenido, separadas por comas (solo contenido HTML)"
|
||||
|
||||
#: ../../content.rst:85
|
||||
msgid "``category``"
|
||||
msgstr ""
|
||||
msgstr "``category``"
|
||||
|
||||
#: ../../content.rst:85
|
||||
msgid "Content category (one only — not multiple)"
|
||||
msgstr ""
|
||||
msgstr "Categoría del contenido (solo una, no varias)"
|
||||
|
||||
#: ../../content.rst:86
|
||||
msgid "``slug``"
|
||||
msgstr ""
|
||||
msgstr "``slug``"
|
||||
|
||||
#: ../../content.rst:86
|
||||
msgid "Identifier used in URLs and translations"
|
||||
msgstr ""
|
||||
msgstr "Identificador usado en URLs y traducciones"
|
||||
|
||||
#: ../../content.rst:87
|
||||
msgid "``author``"
|
||||
msgstr ""
|
||||
msgstr "``author``"
|
||||
|
||||
#: ../../content.rst:87
|
||||
msgid "Content author, when there is only one"
|
||||
msgstr ""
|
||||
msgstr "Autor del contenido, cuando solo hay uno"
|
||||
|
||||
#: ../../content.rst:88
|
||||
msgid "``authors``"
|
||||
msgstr ""
|
||||
msgstr "``authors``"
|
||||
|
||||
#: ../../content.rst:88
|
||||
msgid "Content authors, when there are multiple"
|
||||
msgstr ""
|
||||
msgstr "Autores del contenido, cuando hay varios"
|
||||
|
||||
#: ../../content.rst:89
|
||||
msgid "``summary``"
|
||||
msgstr ""
|
||||
msgstr "``summary``"
|
||||
|
||||
#: ../../content.rst:89
|
||||
msgid "Brief description of content for index pages"
|
||||
msgstr ""
|
||||
msgstr "Descripción breve del contenido para páginas de índice"
|
||||
|
||||
#: ../../content.rst:90
|
||||
msgid "``lang``"
|
||||
msgstr ""
|
||||
msgstr "``lang``"
|
||||
|
||||
#: ../../content.rst:90
|
||||
msgid "Content language ID (``en``, ``fr``, etc.)"
|
||||
msgstr ""
|
||||
msgstr "Identificador del idioma del contenido (``es``, ``fr``, etc.)"
|
||||
|
||||
#: ../../content.rst:91
|
||||
msgid "``translation``"
|
||||
msgstr ""
|
||||
msgstr "``translation``"
|
||||
|
||||
#: ../../content.rst:91
|
||||
msgid "If content is a translation of another (``true`` or ``false``)"
|
||||
msgstr ""
|
||||
msgstr "Si el contenido es una traducción de otro (``true`` o ``false``)"
|
||||
|
||||
#: ../../content.rst:92
|
||||
msgid "``status``"
|
||||
msgstr ""
|
||||
msgstr "``status``"
|
||||
|
||||
#: ../../content.rst:92
|
||||
msgid "Content status: ``draft``, ``hidden``, or ``published``"
|
||||
msgstr ""
|
||||
"Estado del contenido: ``draft`` (borrador), ``hidden`` (oculto), or "
|
||||
"``published`` (publicado)"
|
||||
|
||||
#: ../../content.rst:93
|
||||
msgid "``template``"
|
||||
msgstr ""
|
||||
msgstr "``template``"
|
||||
|
||||
#: ../../content.rst:93
|
||||
msgid "Name of template to use to generate content (without extension)"
|
||||
msgstr ""
|
||||
msgstr "Nombre de la plantilla a usar para generar contenido (sin extensión)"
|
||||
|
||||
#: ../../content.rst:94
|
||||
msgid "``save_as``"
|
||||
msgstr ""
|
||||
msgstr "``save_as``"
|
||||
|
||||
#: ../../content.rst:94
|
||||
msgid "Save content to this relative file path"
|
||||
msgstr ""
|
||||
msgstr "Guardar contenido en esta ruta relativa"
|
||||
|
||||
#: ../../content.rst:95
|
||||
msgid "``url``"
|
||||
msgstr ""
|
||||
msgstr "``url``"
|
||||
|
||||
#: ../../content.rst:95
|
||||
msgid "URL to use for this article/page"
|
||||
msgstr ""
|
||||
msgstr "URL que usar para este artículo/página"
|
||||
|
||||
#: ../../content.rst:98
|
||||
msgid ""
|
||||
"Readers for additional formats (such as AsciiDoc_) are available via plugins. "
|
||||
"Refer to `pelican-plugins`_ repository for those."
|
||||
msgstr ""
|
||||
"Hay disponibles lectores para formatos adicionales (como AsciiDoc_) mediante "
|
||||
"extensiones. Consulta el repositorio `pelican-plugins`_ para usarlos."
|
||||
|
||||
#: ../../content.rst:101
|
||||
msgid ""
|
||||
|
|
@ -253,6 +283,10 @@ msgid ""
|
|||
"``meta`` tags, the title from the ``title`` tag, and the body out from the "
|
||||
"``body`` tag::"
|
||||
msgstr ""
|
||||
"Pelican también puede procesar archivos HTML que acaban en ``.html`` y ``."
|
||||
"htm``. Pelican interpreta el HTML de una manera muy directa, leyendo metadatos "
|
||||
"de etiquetas ```meta``, el título de la etiqueta ``title`` y el cuerpo de la "
|
||||
"etiqueta ``body``::"
|
||||
|
||||
#: ../../content.rst:121
|
||||
msgid ""
|
||||
|
|
@ -261,6 +295,10 @@ msgid ""
|
|||
"the ``keywords`` metadata, as is standard in HTML. The two can be used "
|
||||
"interchangeably."
|
||||
msgstr ""
|
||||
"Con HTML solo hay una simple excepción para los metadatos estándares: las "
|
||||
"etiquetas puede ser especificadas o con el metadato ``tags``, como es estándar "
|
||||
"en Pelican, o con el metadato ```keywords`` como es estándar en HTML. Los dos "
|
||||
"pueden usarse indistintamente."
|
||||
|
||||
#: ../../content.rst:126
|
||||
msgid ""
|
||||
|
|
@ -274,6 +312,16 @@ msgid ""
|
|||
"to ``False``. When parsing dates given in the page metadata, Pelican supports "
|
||||
"the W3C's `suggested subset ISO 8601`__."
|
||||
msgstr ""
|
||||
"Ten en cuenta de que, a excepción del título, ningún de este contenido de "
|
||||
"metadatos es obligatorio: si no se especifica la fecha y ``DEFAULT_DATE`` está "
|
||||
"asignado con ``'fs'``, Pelican se basará en la marca temporal \"mtime\" del "
|
||||
"archivo, y la categoría puede ser determinada por el directorio donde se "
|
||||
"encuentra el archivo. Por ejemplo, un archivo ubicado en ``python/actualidad/mi-"
|
||||
"artículo.rst`` tendrá la categoría ``actualidad``. Si te gustaría organizar tus "
|
||||
"archivos de otras formas en que el nombre de la subcarpeta no sería un buen "
|
||||
"nombre de categoría, puede asignar el ajuste ``USE_FOLDER_AS_CATEGORY`` a "
|
||||
"``False``. A la hora de procesar las fechas proporcionadas en los metadatos de "
|
||||
"página, Pelican soporta el `subconjunto ISO 8601 sugerido`__ por la W3C."
|
||||
|
||||
#: ../../content.rst:136
|
||||
msgid ""
|
||||
|
|
@ -284,6 +332,12 @@ msgid ""
|
|||
"*Publishing via Pelican*. If you would prefer this behavior, add the following "
|
||||
"line to your settings file::"
|
||||
msgstr ""
|
||||
"Así pues, el título es el único metadato requerido. Si eso te molesta, no te "
|
||||
"preocupes. En vez de especificar manualmente el título en tus metadatos cada "
|
||||
"vez, puedes usar el archivo del contenido fuente como el título. Por ejemplo, "
|
||||
"un archivo fuente en Markdown llamado ``Publicando con Pelican.md`` tendría "
|
||||
"automáticamente asignado el título de *Publicando con Pelican*. Si preferirías "
|
||||
"este comportamiento, añade la siguiente línea a tu archivo de ajustes:::"
|
||||
|
||||
#: ../../content.rst:147
|
||||
msgid ""
|
||||
|
|
@ -292,6 +346,11 @@ msgid ""
|
|||
"caching with ``LOAD_CONTENT_CACHE = False`` or use the ``--ignore-cache`` "
|
||||
"command-line switch."
|
||||
msgstr ""
|
||||
"A la hora de experimentar con diferentes ajustes (especialmente los de "
|
||||
"metadatos) el almacenamiento en caché puede interferir y los cambios puede que "
|
||||
"no sean visibles. En esos casos deshabilita el almacenamiento en caché con "
|
||||
"``LOAD_CONTENT_CACHE = False`` o usa el conmutador de línea de comandos ``--"
|
||||
"ignore-cache``."
|
||||
|
||||
#: ../../content.rst:154
|
||||
msgid ""
|
||||
|
|
@ -300,12 +359,19 @@ msgid ""
|
|||
"feed entries in feed readers will be updated automatically when you set "
|
||||
"``modified`` to the current date after you modified your article."
|
||||
msgstr ""
|
||||
"``modified`` debe ser la última vez que actualizaste el artículo, y por defecto "
|
||||
"es ``date`` si no se especifica. Además de poder mostrar ``modified`` en las "
|
||||
"plantillas, las entradas de los lectores de fuentes RSS y Atom se actualizarán "
|
||||
"automáticamente cuando asignes ``modified`` a la la fecha actual después de "
|
||||
"modificar el artículo."
|
||||
|
||||
#: ../../content.rst:159
|
||||
msgid ""
|
||||
"``authors`` is a comma-separated list of article authors. If there's only one "
|
||||
"author you can use ``author`` field."
|
||||
msgstr ""
|
||||
"``authors`` es una lista de los autores del artículo separada por comas. Si "
|
||||
"solo hay un autor, puedes usar el campo ``author``."
|
||||
|
||||
#: ../../content.rst:162
|
||||
msgid ""
|
||||
|
|
@ -313,6 +379,10 @@ msgid ""
|
|||
"``SUMMARY_MAX_LENGTH`` setting can be used to specify how many words from the "
|
||||
"beginning of an article are used as the summary."
|
||||
msgstr ""
|
||||
"Si no especificas explícitamente metadatos de resumen (*summary*) para una "
|
||||
"publicación determinada, el ajuste ``SUMMARY_MAX_LENGTH`` puede utilizarse para "
|
||||
"especificar cuántas palabras desde el principio del artículo son usadas como el "
|
||||
"resumen."
|
||||
|
||||
#: ../../content.rst:166
|
||||
msgid ""
|
||||
|
|
@ -323,16 +393,25 @@ msgid ""
|
|||
"example, if you would like to extract both the date and the slug, you could set "
|
||||
"something like: ``'(?P<date>\\d{4}-\\d{2}-\\d{2})_(?P<slug>.*)'``"
|
||||
msgstr ""
|
||||
"También puedes extraer cualquier metadato del nombre de archivo mediante una "
|
||||
"expresión regular a ser asignada en el ajuste ``FILENAME_METADATA``. Todos los "
|
||||
"grupos nombrados que coincidan serán asignados en el objeto de metadatos. El "
|
||||
"valor predeterminado para el ajuste ``FILENAME_METADATA`` solo extraerá la "
|
||||
"fecha del nombre de archivo. Por ejemplo, si te gustaría extraer tanto la fecha "
|
||||
"como el *slug*, podrías asignar algo como ``'(?P<date>\\d{4}-\\d{2}-\\d{2})_(?"
|
||||
"P<slug>.*)'``"
|
||||
|
||||
#: ../../content.rst:173
|
||||
msgid ""
|
||||
"Please note that the metadata available inside your files takes precedence over "
|
||||
"the metadata extracted from the filename."
|
||||
msgstr ""
|
||||
"Ten en cuenta que los metadatos disponibles dentro de tus archivos tienen "
|
||||
"preferencia sobre los metadatos extraídos del nombre de archivo."
|
||||
|
||||
#: ../../content.rst:177
|
||||
msgid "Pages"
|
||||
msgstr ""
|
||||
msgstr "Páginas"
|
||||
|
||||
#: ../../content.rst:179
|
||||
msgid ""
|
||||
|
|
@ -340,23 +419,31 @@ msgid ""
|
|||
"in it will be used to generate static pages, such as **About** or **Contact** "
|
||||
"pages. (See example filesystem layout below.)"
|
||||
msgstr ""
|
||||
"Si creas un archivo llamado ``pages`` dentro de la carpeta de contenido, todos "
|
||||
"los archivos en ella serán usados para generar páginas estáticas, como páginas "
|
||||
"**Acerca de** y **Contacto**. (Consulta el ejemplo de disposición de archivos "
|
||||
"abajo.)"
|
||||
|
||||
#: ../../content.rst:183
|
||||
msgid ""
|
||||
"You can use the ``DISPLAY_PAGES_ON_MENU`` setting to control whether all those "
|
||||
"pages are displayed in the primary navigation menu. (Default is ``True``.)"
|
||||
msgstr ""
|
||||
"Puedes usar el ajuste ``DISPLAY_PAGES_ON_MENU`` para controlar si todas esas "
|
||||
"páginas se muestran en el menú de navegación primario. (Lo predeterminado es "
|
||||
"``True``.)"
|
||||
|
||||
#: ../../content.rst:186
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"If you want to exclude any pages from being linked to or listed in the menu "
|
||||
"then add a ``status: hidden`` attribute to its metadata. This is useful for "
|
||||
"things like making error pages that fit the generated theme of your site."
|
||||
msgstr ""
|
||||
msgstr "Si quieres"
|
||||
|
||||
#: ../../content.rst:191
|
||||
msgid "Static content"
|
||||
msgstr ""
|
||||
msgstr "Contenido estático"
|
||||
|
||||
#: ../../content.rst:193
|
||||
msgid ""
|
||||
|
|
@ -403,7 +490,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:228
|
||||
msgid "Linking to internal content"
|
||||
msgstr ""
|
||||
msgstr "Enlazar a contenido interno"
|
||||
|
||||
#: ../../content.rst:230
|
||||
msgid ""
|
||||
|
|
@ -432,11 +519,11 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:265
|
||||
msgid "and ``article2.md``::"
|
||||
msgstr ""
|
||||
msgstr "y ``article2.md``::"
|
||||
|
||||
#: ../../content.rst:276
|
||||
msgid "Linking to static files"
|
||||
msgstr ""
|
||||
msgstr "Enlazar a archivos estáticos"
|
||||
|
||||
#: ../../content.rst:278
|
||||
msgid ""
|
||||
|
|
@ -452,7 +539,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:293
|
||||
msgid "``test.md`` would include::"
|
||||
msgstr ""
|
||||
msgstr "``pelicanconf.py`` incluiría::"
|
||||
|
||||
#: ../../content.rst:298
|
||||
msgid ""
|
||||
|
|
@ -469,7 +556,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:306
|
||||
msgid "Attaching static files"
|
||||
msgstr ""
|
||||
msgstr "Adjuntar archivos estáticos"
|
||||
|
||||
#: ../../content.rst:308
|
||||
msgid ""
|
||||
|
|
@ -484,15 +571,15 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:316
|
||||
msgid "This only works for linking to static files."
|
||||
msgstr ""
|
||||
msgstr "Esto solo funciona para enlazar a archivos estáticos."
|
||||
|
||||
#: ../../content.rst:329
|
||||
msgid "``pelicanconf.py`` would include::"
|
||||
msgstr ""
|
||||
msgstr "``pelicanconf.py`` incluiría::"
|
||||
|
||||
#: ../../content.rst:336
|
||||
msgid "``testpost.md`` would include::"
|
||||
msgstr ""
|
||||
msgstr "``testpost.md`` incluiría::"
|
||||
|
||||
#: ../../content.rst:346
|
||||
msgid ""
|
||||
|
|
@ -531,6 +618,22 @@ msgid ""
|
|||
"``STATIC_URL`` settings. (Per-file ``save_as`` and ``url`` overrides can still "
|
||||
"be set in ``EXTRA_PATH_METADATA``.)"
|
||||
msgstr ""
|
||||
"**Ten cuidado a la hora de enlazar un archivo desde varios documentos:** Dado "
|
||||
"que el primer enlace a un archivo finaliza su ubicación y Pelican no define el "
|
||||
"orden en que los documentos son procesados, usar ``{attach}`` en un archivo "
|
||||
"enlazado por muchos documentos puede hacer que su ubicación cambie de una "
|
||||
"generación del sitio a otra. (Si esto pasa en el práctica depende del sistema "
|
||||
"operativo, del sistema de archivos, de la versión de Pelican y los documentos "
|
||||
"añadidos, modificados o eliminados por el proyecto.) Cualquier sitio web que "
|
||||
"enlace a la ubicación antigua del archivo puede que entonces encuentre los "
|
||||
"enlaces rotos. **Por tanto, es recomendable usar {attach} solo si lo usas en "
|
||||
"todos los enlaces a un archivo, y solo si los documentos que enlazan comparten "
|
||||
"un mismo directorio.** Bajo estas condiciones, la ubicación de la salida del "
|
||||
"archivo no cambiará en futuras generaciones. En casos en que no son posibles "
|
||||
"precauciones, considera usar enlaces ``{static}`` en vez de ``{attach}`` y "
|
||||
"dejar que la ubicación del archivo sea determinada por los ajustes del proyecto "
|
||||
"``STATIC_SAVE_AS`` y ``STATIC_URL``. (Por archivo se pueden ajustar "
|
||||
"sobreescrituras de ``save_as`` y ``url`` en ``EXTRA_PATH_METADATA``.)"
|
||||
|
||||
#: ../../content.rst:381
|
||||
msgid ""
|
||||
|
|
@ -540,7 +643,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:385
|
||||
msgid "Linking to authors, categories, index and tags"
|
||||
msgstr ""
|
||||
msgstr "Enlazar a autores, categorías, inicio y etiquetas"
|
||||
|
||||
#: ../../content.rst:387
|
||||
msgid ""
|
||||
|
|
@ -550,7 +653,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:391
|
||||
msgid "Deprecated internal link syntax"
|
||||
msgstr ""
|
||||
msgstr "Sintaxis de enlaces internos obsoleta"
|
||||
|
||||
#: ../../content.rst:393
|
||||
msgid ""
|
||||
|
|
@ -574,6 +677,8 @@ msgstr ""
|
|||
#: ../../content.rst:405
|
||||
msgid "Both Markdown and reStructuredText syntaxes provide mechanisms for this."
|
||||
msgstr ""
|
||||
"Tanto la sintaxis de Markdown como la de reStructuredText proporcionan "
|
||||
"mecanismos para esto."
|
||||
|
||||
#: ../../content.rst:407
|
||||
msgid ""
|
||||
|
|
@ -601,7 +706,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:439
|
||||
msgid "Importing an existing site"
|
||||
msgstr ""
|
||||
msgstr "Importar un sitio web existente"
|
||||
|
||||
#: ../../content.rst:441
|
||||
msgid ""
|
||||
|
|
@ -611,7 +716,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:445
|
||||
msgid "Translations"
|
||||
msgstr ""
|
||||
msgstr "Traducciones"
|
||||
|
||||
#: ../../content.rst:447
|
||||
msgid ""
|
||||
|
|
@ -621,6 +726,11 @@ msgid ""
|
|||
"default language will be listed, and each article will be accompanied by a list "
|
||||
"of available translations for that article."
|
||||
msgstr ""
|
||||
"Es posible traducir artículos. Para hacerlo tienes que añadir un atributo de "
|
||||
"metadato ``lang`` a tus artículos/páginas y asignar el ajuste ``DEFAULT_LANG`` "
|
||||
"(que es inglés [en] por defecto). Con esta configuración, solo se mostrarán los "
|
||||
"artículos con el idioma predeterminado y cada artículo irá acompañado de una "
|
||||
"lista de las traducciones disponibles para ese artículo."
|
||||
|
||||
#: ../../content.rst:455
|
||||
msgid ""
|
||||
|
|
@ -637,19 +747,24 @@ msgid ""
|
|||
"metadata; if not set explicitly, Pelican will auto-generate the slug from the "
|
||||
"title of the article."
|
||||
msgstr ""
|
||||
"Por defecto, Pelican usa la URL del artículo «slug» para determinar si dos o "
|
||||
"más artículos son traducciones. (Esto puede cambiarse con el ajuste "
|
||||
"``ARTICLE_TRANSLATION_ID``.) El *slug* (última parte de una URL limpia) puede "
|
||||
"asignarse manualmente en los metadatos de archivo; si no se asigna "
|
||||
"explícitamente, Pelican autogenerará el *slug* usando el título del artículo."
|
||||
|
||||
#: ../../content.rst:466
|
||||
msgid ""
|
||||
"Here is an example of two articles, one in English and the other in French."
|
||||
msgstr ""
|
||||
msgstr "Aquí va un ejemplo de dos artículos, uno en inglés y el otro en francés."
|
||||
|
||||
#: ../../content.rst:468
|
||||
msgid "The English article::"
|
||||
msgstr ""
|
||||
msgstr "El artículo en inglés::"
|
||||
|
||||
#: ../../content.rst:478
|
||||
msgid "And the French version::"
|
||||
msgstr ""
|
||||
msgstr "Y la versión francesa::"
|
||||
|
||||
#: ../../content.rst:488
|
||||
msgid ""
|
||||
|
|
@ -669,7 +784,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:511
|
||||
msgid "Syntax highlighting"
|
||||
msgstr ""
|
||||
msgstr "Resaltado de sintaxis"
|
||||
|
||||
#: ../../content.rst:513
|
||||
msgid ""
|
||||
|
|
@ -704,33 +819,33 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:544
|
||||
msgid "Option"
|
||||
msgstr ""
|
||||
msgstr "Opción"
|
||||
|
||||
#: ../../content.rst:544
|
||||
msgid "Valid values"
|
||||
msgstr ""
|
||||
msgstr "Valores válidos"
|
||||
|
||||
#: ../../content.rst:546
|
||||
msgid "anchorlinenos"
|
||||
msgstr ""
|
||||
msgstr "anchorlinenos"
|
||||
|
||||
#: ../../content.rst:546 ../../content.rst:570 ../../content.rst:572
|
||||
msgid "N/A"
|
||||
msgstr ""
|
||||
msgstr "sin valor"
|
||||
|
||||
#: ../../content.rst:546
|
||||
msgid "If present wrap line numbers in <a> tags."
|
||||
msgstr ""
|
||||
msgstr "Si está presente, incluir los números de línea en etiquetas <a>."
|
||||
|
||||
#: ../../content.rst:547
|
||||
msgid "classprefix"
|
||||
msgstr ""
|
||||
msgstr "classprefix"
|
||||
|
||||
#: ../../content.rst:547 ../../content.rst:555 ../../content.rst:557
|
||||
#: ../../content.rst:566 ../../content.rst:568 ../../content.rst:573
|
||||
#: ../../content.rst:574
|
||||
msgid "string"
|
||||
msgstr ""
|
||||
msgstr "cadena"
|
||||
|
||||
#: ../../content.rst:547
|
||||
msgid "String to prepend to token class names"
|
||||
|
|
@ -738,11 +853,11 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:548
|
||||
msgid "hl_lines"
|
||||
msgstr ""
|
||||
msgstr "hl_lines"
|
||||
|
||||
#: ../../content.rst:548
|
||||
msgid "numbers"
|
||||
msgstr ""
|
||||
msgstr "números"
|
||||
|
||||
#: ../../content.rst:548
|
||||
msgid ""
|
||||
|
|
@ -754,7 +869,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:555
|
||||
msgid "lineanchors"
|
||||
msgstr ""
|
||||
msgstr "lineanchors"
|
||||
|
||||
#: ../../content.rst:555
|
||||
msgid "Wrap each line in an anchor using this string and -linenumber."
|
||||
|
|
@ -762,7 +877,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:557
|
||||
msgid "linenos"
|
||||
msgstr ""
|
||||
msgstr "linenos"
|
||||
|
||||
#: ../../content.rst:557
|
||||
msgid ""
|
||||
|
|
@ -773,11 +888,11 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:562
|
||||
msgid "linenospecial"
|
||||
msgstr ""
|
||||
msgstr "linenospecial"
|
||||
|
||||
#: ../../content.rst:562 ../../content.rst:564 ../../content.rst:565
|
||||
msgid "number"
|
||||
msgstr ""
|
||||
msgstr "número"
|
||||
|
||||
#: ../../content.rst:562
|
||||
msgid "If set every nth line will be given the 'special' css class."
|
||||
|
|
@ -785,7 +900,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:564
|
||||
msgid "linenostart"
|
||||
msgstr ""
|
||||
msgstr "linenostart"
|
||||
|
||||
#: ../../content.rst:564
|
||||
msgid "Line number for the first line."
|
||||
|
|
@ -793,23 +908,24 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:565
|
||||
msgid "linenostep"
|
||||
msgstr ""
|
||||
msgstr "linenostep"
|
||||
|
||||
#: ../../content.rst:565
|
||||
#, fuzzy
|
||||
msgid "Print every nth line number."
|
||||
msgstr ""
|
||||
msgstr "Imprime cada"
|
||||
|
||||
#: ../../content.rst:566
|
||||
msgid "lineseparator"
|
||||
msgstr ""
|
||||
msgstr "lineseparator"
|
||||
|
||||
#: ../../content.rst:566
|
||||
msgid "String to print between lines of code, '\\n' by default."
|
||||
msgstr ""
|
||||
msgstr "Cadena a imprimir entre líneas de código, '\\n' por defecto."
|
||||
|
||||
#: ../../content.rst:568
|
||||
msgid "linespans"
|
||||
msgstr ""
|
||||
msgstr "linespans"
|
||||
|
||||
#: ../../content.rst:568
|
||||
msgid "Wrap each line in a span using this and -linenumber."
|
||||
|
|
@ -817,7 +933,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:570
|
||||
msgid "nobackground"
|
||||
msgstr ""
|
||||
msgstr "nobackground"
|
||||
|
||||
#: ../../content.rst:570
|
||||
msgid "If set do not output background color for the wrapping element"
|
||||
|
|
@ -825,7 +941,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:572
|
||||
msgid "nowrap"
|
||||
msgstr ""
|
||||
msgstr "nowrap"
|
||||
|
||||
#: ../../content.rst:572
|
||||
msgid "If set do not wrap the tokens at all."
|
||||
|
|
@ -837,7 +953,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:573
|
||||
msgid "ctags file to use for name definitions."
|
||||
msgstr ""
|
||||
msgstr "archivo *ctags* a usar para definiciones de nombres."
|
||||
|
||||
#: ../../content.rst:574
|
||||
msgid "tagurlformat"
|
||||
|
|
@ -883,7 +999,7 @@ msgstr ""
|
|||
|
||||
#: ../../content.rst:606
|
||||
msgid "Publishing drafts"
|
||||
msgstr ""
|
||||
msgstr "Publicar borradores"
|
||||
|
||||
#: ../../content.rst:608
|
||||
msgid ""
|
||||
|
|
@ -905,6 +1021,8 @@ msgid ""
|
|||
"To publish a post when the default status is ``draft``, update the post's "
|
||||
"metadata to include ``Status: published``."
|
||||
msgstr ""
|
||||
"Para publicar una entrada cuando el estado predeterminado es ``draft``, "
|
||||
"actualiza los metadatos de la publicación para incluir ``Status: published``."
|
||||
|
||||
#: ../../content.rst:625
|
||||
msgid "Hidden Posts"
|
||||
|
|
|
|||
|
|
@ -3,62 +3,69 @@
|
|||
# This file is distributed under the same license as the Pelican package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, 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 <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
"PO-Revision-Date: 2023-01-05 12:52+0100\n"
|
||||
"Last-Translator: \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"
|
||||
|
||||
#: ../../faq.rst:2
|
||||
msgid "Frequently Asked Questions (FAQ)"
|
||||
msgstr ""
|
||||
msgstr "Preguntas frecuentes"
|
||||
|
||||
#: ../../faq.rst:4
|
||||
msgid "Here are some frequently asked questions about Pelican."
|
||||
msgstr ""
|
||||
msgstr "Aquí hay algunas preguntas frecuentes sobre Pelican."
|
||||
|
||||
#: ../../faq.rst:7
|
||||
msgid "What's the best way to communicate a problem, question, or suggestion?"
|
||||
msgstr ""
|
||||
"¿Cuál es la mejor forma de comunicar un problema, una pregunta o sugerencia?"
|
||||
|
||||
#: ../../faq.rst:9
|
||||
msgid "Please read our :doc:`feedback guidelines <contribute>`."
|
||||
msgstr ""
|
||||
msgstr "Por favor lee nuestras :doc:`directrices de *feedback* <contribute>`."
|
||||
|
||||
#: ../../faq.rst:12
|
||||
msgid "How can I help?"
|
||||
msgstr ""
|
||||
msgstr "¿Cómo puedo ayudar?"
|
||||
|
||||
#: ../../faq.rst:14
|
||||
msgid ""
|
||||
"There are several ways to help out. First, you can communicate any "
|
||||
"Pelican suggestions or problems you might have via `Pelican Discussions "
|
||||
"<https://github.com/getpelican/pelican/discussions>`_. Please first check"
|
||||
" the existing list of discussions and issues (both open and closed) in "
|
||||
"order to avoid submitting topics that have already been covered before."
|
||||
"There are several ways to help out. First, you can communicate any Pelican "
|
||||
"suggestions or problems you might have via `Pelican Discussions <https://"
|
||||
"github.com/getpelican/pelican/discussions>`_. Please first check the existing "
|
||||
"list of discussions and issues (both open and closed) in order to avoid "
|
||||
"submitting topics that have already been covered before."
|
||||
msgstr ""
|
||||
"Hay varias maneras de ayudar. Primero, puedes comunicar cualquier sugerencias "
|
||||
"o problemas de Pelican que tengas mediante `Pelican Discussions <https://"
|
||||
"github.com/getpelican/pelican/discussions>`_. Por favor, primero comprueba la "
|
||||
"lista existente de discusiones y problemas (tanto abiertos como cerrados) para "
|
||||
"evitar enviar temas que hayan sido tratados anteriormente."
|
||||
|
||||
#: ../../faq.rst:20
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"If you want to contribute, please fork `the git repository "
|
||||
"<https://github.com/getpelican/pelican/>`_, 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 "
|
||||
"<contribute>` section for more details."
|
||||
msgstr ""
|
||||
"If you want to contribute, please fork `the git repository <https://github.com/"
|
||||
"getpelican/pelican/>`_, 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 <contribute>` section for more "
|
||||
"details."
|
||||
msgstr "Si quieres contribuir, "
|
||||
|
||||
#: ../../faq.rst:26
|
||||
msgid ""
|
||||
"You can also contribute by creating themes and improving the "
|
||||
"documentation."
|
||||
"You can also contribute by creating themes and improving the documentation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:29
|
||||
|
|
@ -68,9 +75,8 @@ msgstr ""
|
|||
#: ../../faq.rst:31
|
||||
msgid ""
|
||||
"Configuration files are optional and are just an easy way to configure "
|
||||
"Pelican. For basic operations, it's possible to specify options while "
|
||||
"invoking Pelican via the command line. See ``pelican --help`` for more "
|
||||
"information."
|
||||
"Pelican. For basic operations, it's possible to specify options while invoking "
|
||||
"Pelican via the command line. See ``pelican --help`` for more information."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:36
|
||||
|
|
@ -79,10 +85,10 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:38
|
||||
msgid ""
|
||||
"When experimenting with different settings (especially the metadata ones)"
|
||||
" caching may interfere and the changes may not be visible. In such cases,"
|
||||
" ensure that caching is disabled via ``LOAD_CONTENT_CACHE = False`` or "
|
||||
"use the ``--ignore-cache`` command-line switch."
|
||||
"When experimenting with different settings (especially the metadata ones) "
|
||||
"caching may interfere and the changes may not be visible. In such cases, "
|
||||
"ensure that caching is disabled via ``LOAD_CONTENT_CACHE = False`` or use the "
|
||||
"``--ignore-cache`` command-line switch."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:44
|
||||
|
|
@ -91,20 +97,19 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:46
|
||||
msgid ""
|
||||
"Pygments adds some classes to the generated content. These classes are "
|
||||
"used by themes to style code syntax highlighting via CSS. Specifically, "
|
||||
"you can customize the appearance of your syntax highlighting via the "
|
||||
"``.highlight pre`` class in your theme's CSS file. To see how various "
|
||||
"styles can be used to render Django code, for example, use the style "
|
||||
"selector drop-down at top-right on the `Pygments project demo site "
|
||||
"<https://pygments.org/demo/>`_."
|
||||
"Pygments adds some classes to the generated content. These classes are used by "
|
||||
"themes to style code syntax highlighting via CSS. Specifically, you can "
|
||||
"customize the appearance of your syntax highlighting via the ``.highlight "
|
||||
"pre`` class in your theme's CSS file. To see how various styles can be used to "
|
||||
"render Django code, for example, use the style selector drop-down at top-right "
|
||||
"on the `Pygments project demo site <https://pygments.org/demo/>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:53
|
||||
msgid ""
|
||||
"You can use the following example commands to generate a starting CSS "
|
||||
"file from a Pygments built-in style (in this case, \"monokai\") and then "
|
||||
"copy the generated CSS file to your new theme::"
|
||||
"You can use the following example commands to generate a starting CSS file "
|
||||
"from a Pygments built-in style (in this case, \"monokai\") and then copy the "
|
||||
"generated CSS file to your new theme::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:60
|
||||
|
|
@ -121,44 +126,42 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:68
|
||||
msgid "I want to use Markdown, but I got an error."
|
||||
msgstr ""
|
||||
msgstr "Quiero usar Markdown, pero obtengo un error."
|
||||
|
||||
#: ../../faq.rst:70
|
||||
msgid ""
|
||||
"If you try to generate Markdown content without first installing the "
|
||||
"Markdown library, may see a message that says ``No valid files found in "
|
||||
"content``. Markdown is not a hard dependency for Pelican, so if you have "
|
||||
"content in Markdown format, you will need to explicitly install the "
|
||||
"Markdown library. You can do so by typing the following command, "
|
||||
"prepending ``sudo`` if permissions require it::"
|
||||
"If you try to generate Markdown content without first installing the Markdown "
|
||||
"library, may see a message that says ``No valid files found in content``. "
|
||||
"Markdown is not a hard dependency for Pelican, so if you have content in "
|
||||
"Markdown format, you will need to explicitly install the Markdown library. You "
|
||||
"can do so by typing the following command, prepending ``sudo`` if permissions "
|
||||
"require it::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:80
|
||||
msgid "Can I use arbitrary metadata in my templates?"
|
||||
msgstr ""
|
||||
msgstr "¿Puedo usar metadatos arbitrarios en mis plantillas?"
|
||||
|
||||
#: ../../faq.rst:82
|
||||
msgid ""
|
||||
"Yes. For example, to include a modified date in a Markdown post, one "
|
||||
"could include the following at the top of the article::"
|
||||
"Yes. For example, to include a modified date in a Markdown post, one could "
|
||||
"include the following at the top of the article::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:87
|
||||
msgid ""
|
||||
"For reStructuredText, this metadata should of course be prefixed with a "
|
||||
"colon::"
|
||||
"For reStructuredText, this metadata should of course be prefixed with a colon::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:91
|
||||
msgid ""
|
||||
"This metadata can then be accessed in templates such as ``article.html`` "
|
||||
"via::"
|
||||
"This metadata can then be accessed in templates such as ``article.html`` via::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../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::"
|
||||
"If you want to include metadata in templates outside the article context (e."
|
||||
"g., ``base.html``), the ``if`` statement should instead be::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:103
|
||||
|
|
@ -167,9 +170,9 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:105
|
||||
msgid ""
|
||||
"It's as simple as adding an extra line of metadata to any page or article"
|
||||
" that you want to have its own template. For example, this is how it "
|
||||
"would be handled for content in reST format::"
|
||||
"It's as simple as adding an extra line of metadata to any page or article that "
|
||||
"you want to have its own template. For example, this is how it would be "
|
||||
"handled for content in reST format::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:111
|
||||
|
|
@ -188,16 +191,14 @@ msgstr ""
|
|||
|
||||
#: ../../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::"
|
||||
"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 ""
|
||||
|
||||
#: ../../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."
|
||||
"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 ""
|
||||
|
||||
#: ../../faq.rst:134
|
||||
|
|
@ -206,16 +207,16 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:136
|
||||
msgid ""
|
||||
"The override feature mentioned above can be used to specify a static page"
|
||||
" as your home page. The following Markdown example could be stored in "
|
||||
"``content/pages/home.md``::"
|
||||
"The override feature mentioned above can be used to specify a static page as "
|
||||
"your home page. The following Markdown example could be stored in ``content/"
|
||||
"pages/home.md``::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:146
|
||||
msgid ""
|
||||
"If the original blog index is still wanted, it can then be saved in a "
|
||||
"different location by setting ``INDEX_SAVE_AS = 'blog_index.html'`` for "
|
||||
"the ``'index'`` direct template."
|
||||
"different location by setting ``INDEX_SAVE_AS = 'blog_index.html'`` for the "
|
||||
"``'index'`` direct template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:151
|
||||
|
|
@ -224,10 +225,9 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:153
|
||||
msgid ""
|
||||
"To disable feed generation, all feed settings should be set to ``None``. "
|
||||
"All 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::"
|
||||
"To disable feed generation, all feed settings should be set to ``None``. All "
|
||||
"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 ""
|
||||
|
||||
#: ../../faq.rst:163
|
||||
|
|
@ -238,22 +238,20 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:167
|
||||
msgid ""
|
||||
"I'm getting a warning about feeds generated without SITEURL being set "
|
||||
"properly"
|
||||
"I'm getting a warning about feeds generated without SITEURL being set properly"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:169
|
||||
msgid ""
|
||||
"`RSS and Atom feeds require all URL links to be absolute "
|
||||
"<https://validator.w3.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."
|
||||
"`RSS and Atom feeds require all URL links to be absolute <https://validator.w3."
|
||||
"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 ""
|
||||
|
||||
#: ../../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."
|
||||
"Feeds are still generated when this warning is displayed, but links within may "
|
||||
"be malformed and thus the feed may not validate."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:178
|
||||
|
|
@ -262,16 +260,15 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:180
|
||||
msgid ""
|
||||
"Instead of having to open a separate browser window to read articles, the"
|
||||
" overwhelming majority of folks who use feed readers prefer to read "
|
||||
"content within the feed reader itself. Mainly for that reason, Pelican "
|
||||
"does not support restricting Atom feeds to only contain summaries. Unlike"
|
||||
" Atom feeds, the RSS feed specification does not include a separate "
|
||||
"``content`` field, so by default Pelican publishes RSS feeds that only "
|
||||
"contain summaries (but can optionally be set to instead publish full "
|
||||
"content RSS feeds). So the default feed generation behavior provides "
|
||||
"users with a choice: subscribe to Atom feeds for full content or to RSS "
|
||||
"feeds for just the summaries."
|
||||
"Instead of having to open a separate browser window to read articles, the "
|
||||
"overwhelming majority of folks who use feed readers prefer to read content "
|
||||
"within the feed reader itself. Mainly for that reason, Pelican does not "
|
||||
"support restricting Atom feeds to only contain summaries. Unlike Atom feeds, "
|
||||
"the RSS feed specification does not include a separate ``content`` field, so "
|
||||
"by default Pelican publishes RSS feeds that only contain summaries (but can "
|
||||
"optionally be set to instead publish full content RSS feeds). So the default "
|
||||
"feed generation behavior provides users with a choice: subscribe to Atom feeds "
|
||||
"for full content or to RSS feeds for just the summaries."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:191
|
||||
|
|
@ -280,48 +277,44 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:193
|
||||
msgid ""
|
||||
"No. Pelican can be easily configured to create and maintain any type of "
|
||||
"static site. This may require a little customization of your theme and "
|
||||
"Pelican configuration. For example, if you are building a launch site for"
|
||||
" your product 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::"
|
||||
"No. Pelican can be easily configured to create and maintain any type of static "
|
||||
"site. This may require a little customization of your theme and Pelican "
|
||||
"configuration. For example, if you are building a launch site for your product "
|
||||
"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 ""
|
||||
|
||||
#: ../../faq.rst:203
|
||||
msgid ""
|
||||
"Why does Pelican always write all HTML files even with content caching "
|
||||
"enabled?"
|
||||
"Why does Pelican always write all HTML files even with content caching enabled?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:205
|
||||
msgid ""
|
||||
"In order to reliably determine whether the HTML output is different "
|
||||
"before writing it, a large part of the generation environment including "
|
||||
"the template contexts, imported plugins, etc. would have to be saved and "
|
||||
"compared, at least in the form of a hash (which would require special "
|
||||
"handling of unhashable types), because of all the possible combinations "
|
||||
"of plugins, pagination, etc. which may change in many different ways. "
|
||||
"This would require a lot more processing time and memory and storage "
|
||||
"space. Simply writing the files each time is a lot faster and a lot more "
|
||||
"reliable."
|
||||
"In order to reliably determine whether the HTML output is different before "
|
||||
"writing it, a large part of the generation environment including the template "
|
||||
"contexts, imported plugins, etc. would have to be saved and compared, at least "
|
||||
"in the form of a hash (which would require special handling of unhashable "
|
||||
"types), because of all the possible combinations of plugins, pagination, etc. "
|
||||
"which may change in many different ways. This would require a lot more "
|
||||
"processing time and memory and storage space. Simply writing the files each "
|
||||
"time is a lot faster and a lot more reliable."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:214
|
||||
msgid ""
|
||||
"However, this means that the modification time of the files changes every"
|
||||
" time, so a ``rsync`` based upload will transfer them even if their "
|
||||
"content hasn't changed. A simple solution is to make ``rsync`` use the "
|
||||
"``--checksum`` option, which will make it compare the file checksums in a"
|
||||
" much faster way than Pelican would."
|
||||
"However, this means that the modification time of the files changes every "
|
||||
"time, so a ``rsync`` based upload will transfer them even if their content "
|
||||
"hasn't changed. A simple solution is to make ``rsync`` use the ``--checksum`` "
|
||||
"option, which will make it compare the file checksums in a much faster way "
|
||||
"than Pelican would."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:220
|
||||
msgid ""
|
||||
"When only several specific output files are of interest (e.g. when "
|
||||
"working on some specific page or the theme templates), the "
|
||||
"``WRITE_SELECTED`` option may help, see "
|
||||
":ref:`writing_only_selected_content`."
|
||||
"When only several specific output files are of interest (e.g. when working on "
|
||||
"some specific page or the theme templates), the ``WRITE_SELECTED`` option may "
|
||||
"help, see :ref:`writing_only_selected_content`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:225
|
||||
|
|
@ -330,11 +323,10 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:227
|
||||
msgid ""
|
||||
"It is often useful to process only e.g. 10 articles for debugging "
|
||||
"purposes. This can be achieved by explicitly specifying only the "
|
||||
"filenames of those 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``."
|
||||
"It is often useful to process only e.g. 10 articles for debugging purposes. "
|
||||
"This can be achieved by explicitly specifying only the filenames of those "
|
||||
"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 ""
|
||||
|
||||
#: ../../faq.rst:233
|
||||
|
|
@ -343,10 +335,10 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:235
|
||||
msgid ""
|
||||
"In an ongoing effort to streamline Pelican, tag cloud generation has been"
|
||||
" moved out of Pelican core and into a separate `plugin "
|
||||
"<https://github.com/pelican-plugins/tag-cloud>`_. See the :ref:`plugins` "
|
||||
"documentation for further information about the Pelican plugin system."
|
||||
"In an ongoing effort to streamline Pelican, tag cloud generation has been "
|
||||
"moved out of Pelican core and into a separate `plugin <https://github.com/"
|
||||
"pelican-plugins/tag-cloud>`_. See the :ref:`plugins` documentation for further "
|
||||
"information about the Pelican plugin system."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:241
|
||||
|
|
@ -355,11 +347,10 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:243
|
||||
msgid ""
|
||||
"Pages were available to themes as lowercase ``pages`` and uppercase "
|
||||
"``PAGES``. To bring this inline with the :ref:`templates-variables` "
|
||||
"section, ``PAGES`` has been removed. This is quickly resolved by updating"
|
||||
" your theme to iterate over ``pages`` instead of ``PAGES``. Just "
|
||||
"replace::"
|
||||
"Pages were available to themes as lowercase ``pages`` and uppercase ``PAGES``. "
|
||||
"To bring this inline with the :ref:`templates-variables` section, ``PAGES`` "
|
||||
"has been removed. This is quickly resolved by updating your theme to iterate "
|
||||
"over ``pages`` instead of ``PAGES``. Just replace::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:250
|
||||
|
|
@ -372,19 +363,17 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:257
|
||||
msgid ""
|
||||
"Pelican's article and page generators run before it's static generator. "
|
||||
"That means if you use a setup similar to the default configuration, where"
|
||||
" a static source directory is defined inside a ``*_PATHS`` setting, all "
|
||||
"files that have a valid content file ending (``.html``, ``.rst``, "
|
||||
"``.md``, ...) will be treated as articles or pages before they get "
|
||||
"treated as static files."
|
||||
"Pelican's article and page generators run before it's static generator. That "
|
||||
"means if you use a setup similar to the default configuration, where a static "
|
||||
"source directory is defined inside a ``*_PATHS`` setting, all files that have "
|
||||
"a valid content file ending (``.html``, ``.rst``, ``.md``, ...) will be "
|
||||
"treated as articles or pages before they get treated as static files."
|
||||
msgstr ""
|
||||
|
||||
#: ../../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."
|
||||
"To circumvent this issue either use the appropriate ``*_EXCLUDES`` setting or "
|
||||
"disable the offending reader via ``READERS`` if you don't need it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../faq.rst:267
|
||||
|
|
@ -393,14 +382,13 @@ msgstr ""
|
|||
|
||||
#: ../../faq.rst:269
|
||||
msgid ""
|
||||
"Pelican does not directly handle Markdown processing and instead "
|
||||
"delegates that task to the Python-Markdown_ project, the core of which "
|
||||
"purposefully follows the original Markdown syntax rules and not the "
|
||||
"myriad Markdown \"flavors\" that have subsequently propagated. That said,"
|
||||
" Python-Markdown_ is quite modular, and the syntax you are looking for "
|
||||
"may be provided by one of the many available `Markdown Extensions`_. "
|
||||
"Alternatively, some folks have created Pelican plugins that support "
|
||||
"Markdown variants, so that may be your best choice if there is a "
|
||||
"particular variant you want to use when writing your content."
|
||||
"Pelican does not directly handle Markdown processing and instead delegates "
|
||||
"that task to the Python-Markdown_ project, the core of which purposefully "
|
||||
"follows the original Markdown syntax rules and not the myriad Markdown "
|
||||
"\"flavors\" that have subsequently propagated. That said, Python-Markdown_ is "
|
||||
"quite modular, and the syntax you are looking for may be provided by one of "
|
||||
"the many available `Markdown Extensions`_. Alternatively, some folks have "
|
||||
"created Pelican plugins that support Markdown variants, so that may be your "
|
||||
"best choice if there is a particular variant you want to use when writing your "
|
||||
"content."
|
||||
msgstr ""
|
||||
|
||||
|
|
|
|||
|
|
@ -3,34 +3,37 @@
|
|||
# This file is distributed under the same license as the Pelican package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, 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 <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
"PO-Revision-Date: 2023-01-05 13:24+0100\n"
|
||||
"Last-Translator: \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"
|
||||
|
||||
#: ../../internals.rst:2
|
||||
msgid "Pelican internals"
|
||||
msgstr ""
|
||||
msgstr "Funcionamiento interno de Pelican"
|
||||
|
||||
#: ../../internals.rst:4
|
||||
msgid ""
|
||||
"This section describe how Pelican works internally. As you'll see, it's "
|
||||
"quite simple, but a bit of documentation doesn't hurt. :)"
|
||||
msgstr ""
|
||||
"Esta sección describe cómo Pelican funciona internamente. Como verás, es "
|
||||
"bastante simple, pero un poco de documentación no hace daño. :)"
|
||||
|
||||
#: ../../internals.rst:7
|
||||
msgid ""
|
||||
"You can also find in the :doc:`report` section an excerpt of a report the"
|
||||
" original author wrote with some software design information."
|
||||
"You can also find in the :doc:`report` section an excerpt of a report "
|
||||
"the original author wrote with some software design information."
|
||||
msgstr ""
|
||||
|
||||
#: ../../internals.rst:13
|
||||
|
|
@ -39,10 +42,10 @@ msgstr ""
|
|||
|
||||
#: ../../internals.rst:15
|
||||
msgid ""
|
||||
"What Pelican does is take a list of files and process them into some sort"
|
||||
" of output. Usually, the input files are reStructuredText and Markdown "
|
||||
"files, and the output is a blog, but both input and output can be "
|
||||
"anything you want."
|
||||
"What Pelican does is take a list of files and process them into some "
|
||||
"sort of output. Usually, the input files are reStructuredText and "
|
||||
"Markdown files, and the output is a blog, but both input and output can "
|
||||
"be anything you want."
|
||||
msgstr ""
|
||||
|
||||
#: ../../internals.rst:19
|
||||
|
|
@ -85,18 +88,18 @@ msgstr ""
|
|||
|
||||
#: ../../internals.rst:41
|
||||
msgid ""
|
||||
"Is there an awesome markup language you want to add to Pelican? Well, the"
|
||||
" only thing you have to do is to create a class with a ``read`` method "
|
||||
"that returns HTML content and some metadata."
|
||||
"Is there an awesome markup language you want to add to Pelican? Well, "
|
||||
"the only thing you have to do is to create a class with a ``read`` "
|
||||
"method that returns HTML content and some metadata."
|
||||
msgstr ""
|
||||
|
||||
#: ../../internals.rst:45
|
||||
msgid "Take a look at the Markdown reader::"
|
||||
msgstr ""
|
||||
msgstr "Échale un vistazo al lector de Markdown::"
|
||||
|
||||
#: ../../internals.rst:71
|
||||
msgid "Simple, isn't it?"
|
||||
msgstr ""
|
||||
msgstr "Simple, ¿no?"
|
||||
|
||||
#: ../../internals.rst:73
|
||||
msgid ""
|
||||
|
|
@ -110,13 +113,14 @@ msgstr ""
|
|||
|
||||
#: ../../internals.rst:80
|
||||
msgid "How to implement a new generator?"
|
||||
msgstr ""
|
||||
msgstr "¿Cómo implementar un nuevo generador?"
|
||||
|
||||
#: ../../internals.rst:82
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"Generators have two important methods. You're not forced to create both; "
|
||||
"only the existing ones will be called."
|
||||
msgstr ""
|
||||
msgstr "Los generadores tienen dos métodos importantes. "
|
||||
|
||||
#: ../../internals.rst:85
|
||||
msgid ""
|
||||
|
|
@ -136,8 +140,7 @@ msgid ""
|
|||
"generating the output. :) It's here that you may want to look at the "
|
||||
"context and call the methods of the ``writer`` object that is passed as "
|
||||
"the first argument of this function. In the ``PageGenerator`` example, "
|
||||
"this method will look at all the pages recorded in the global context and"
|
||||
" output a file on the disk (using the writer method ``write_file``) for "
|
||||
"each page encountered."
|
||||
"this method will look at all the pages recorded in the global context "
|
||||
"and output a file on the disk (using the writer method ``write_file``) "
|
||||
"for each page encountered."
|
||||
msgstr ""
|
||||
|
||||
|
|
|
|||
|
|
@ -3,19 +3,20 @@
|
|||
# This file is distributed under the same license as the Pelican package.
|
||||
# FIRST AUTHOR <EMAIL@ADDRESS>, 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 <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
"PO-Revision-Date: 2023-01-05 12:33+0100\n"
|
||||
"Last-Translator: \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"
|
||||
|
||||
#: ../../pelican-themes.rst:2
|
||||
msgid "pelican-themes"
|
||||
|
|
@ -23,7 +24,7 @@ msgstr ""
|
|||
|
||||
#: ../../pelican-themes.rst:7
|
||||
msgid "Description"
|
||||
msgstr ""
|
||||
msgstr "Descripción"
|
||||
|
||||
#: ../../pelican-themes.rst:9
|
||||
msgid ""
|
||||
|
|
@ -33,7 +34,7 @@ msgstr ""
|
|||
|
||||
#: ../../pelican-themes.rst:14
|
||||
msgid "Usage"
|
||||
msgstr ""
|
||||
msgstr "Uso"
|
||||
|
||||
#: ../../pelican-themes.rst:16
|
||||
msgid "pelican-themes [-h] [-l] [-i theme path [theme path ...]]"
|
||||
|
|
@ -103,15 +104,15 @@ msgstr ""
|
|||
|
||||
#: ../../pelican-themes.rst:65
|
||||
msgid ""
|
||||
"``two-column`` is prefixed with an ``@`` because this theme is not copied"
|
||||
" to the Pelican theme path, but is instead just linked to it (see "
|
||||
"``two-column`` is prefixed with an ``@`` because this theme is not "
|
||||
"copied to the Pelican theme path, but is instead just linked to it (see "
|
||||
"`Creating symbolic links`_ for details about creating symbolic links)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../pelican-themes.rst:69
|
||||
msgid ""
|
||||
"Note that you can combine the ``--list`` option with the ``-v`` or "
|
||||
"``--verbose`` option to get more verbose output, like this:"
|
||||
"Note that you can combine the ``--list`` option with the ``-v`` or ``--"
|
||||
"verbose`` option to get more verbose output, like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../pelican-themes.rst:81
|
||||
|
|
@ -170,9 +171,9 @@ msgstr ""
|
|||
|
||||
#: ../../pelican-themes.rst:157
|
||||
msgid ""
|
||||
"The ``--install``, ``--remove`` and ``--symlink`` option are not mutually"
|
||||
" exclusive, so you can combine them in the same command line to do more "
|
||||
"than one operation at time, like this:"
|
||||
"The ``--install``, ``--remove`` and ``--symlink`` option are not "
|
||||
"mutually exclusive, so you can combine them in the same command line to "
|
||||
"do more than one operation at time, like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../pelican-themes.rst:169
|
||||
|
|
@ -180,4 +181,3 @@ msgid ""
|
|||
"In this example, the theme ``notmyidea-cms`` is replaced by the theme "
|
||||
"``notmyidea-cms-fr``"
|
||||
msgstr ""
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue