File: index.html

package info (click to toggle)
ruby-jekyll-polyglot 1.9.0-1
links: PTS, VCS
area: main
in suites: forky, sid, trixie
size: 5,196 kB
sloc: xml: 1,500; ruby: 947; sh: 10; makefile: 4
file content (416 lines) | stat: -rw-r--r-- 29,393 bytes
parent folder | download | duplicates (2)
<!DOCTYPE html>
<html lang="en-us">

  <head>
  
  <link href="http://gmpg.org/xfn/11" rel="profile">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta http-equiv="content-type" content="text/html; charset=utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="title" content="Home &middot; Polyglot">
  <meta name="description" content="Un plugin soporte de i18n para Jekyll que hace soporte de internacionalización rápida e intuitiva, para los blogs grandes y pequeños.">
  <meta name="keywords" content="multilingüe, i18n, jekyll, políglota, rápido, intuitivo, untra, github, páginas, blog, plugin, ruby, gem, internacionalización, localización, traducción, idioma, soporte, multilingüe, multilingüe">
  <meta http-equiv="Content-Language" content="es">
<link rel="alternate" hreflang="en" href="https://polyglot.untra.io/"/>
<link rel="alternate" hreflang="es" href="https://polyglot.untra.io/es/"/>
<link rel="alternate" hreflang="de" href="https://polyglot.untra.io/de/"/>
<link rel="alternate" hreflang="fr" href="https://polyglot.untra.io/fr/"/>
<link rel="alternate" hreflang="ru" href="https://polyglot.untra.io/ru/"/>
<link rel="alternate" hreflang="nl" href="https://polyglot.untra.io/nl/"/>
<link rel="alternate" hreflang="he" href="https://polyglot.untra.io/he/"/>
<link rel="alternate" hreflang="ko" href="https://polyglot.untra.io/ko/"/>
<link rel="alternate" hreflang="zh-CN" href="https://polyglot.untra.io/zh-CN/"/>
<link rel="alternate" hreflang="pt-BR" href="https://polyglot.untra.io/pt-BR/"/>

  <title>
    
      Polyglot &middot; Straightforward I18n for Jekyll Blogs
    
  </title>

  <!-- CSS -->
  <link rel="stylesheet" href="/public/css/poole.css">
  <link rel="stylesheet" href="/public/css/syntax.css">
  <link rel="stylesheet" href="/public/css/hyde.css">
  <link rel="stylesheet" href="/public/css/custom.css">
  <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=PT+Sans:400,400italic,700|Abril+Fatface">

  <!-- Icons -->
  <link rel="apple-touch-icon-precomposed" sizes="144x144" href="/public/apple-touch-icon-144-precomposed.png">
                                 <link rel="shortcut icon" href="/public/favicon.ico">

  <!-- RSS -->
  <link rel="alternate" type="application/rss+xml" title="RSS" href="/es/atom.xml">
</head>


  <body theme-base-08>

    
<div class="sidebar">
  <div class="container sidebar-sticky">
    <div class="sidebar-about">
      <p class="speech">¡hola!</p>
    </br>
      <h1>
        <a href="">
          Polyglot
        </a>
      </h1>
      <p class="lead">Un plugin soporte de i18n para <a href="http://jekyllrb.com" target="_blank">Jekyll</a> que hace soporte de internacionalización rápida e intuitiva, para los blogs grandes y pequeños. Hecho por <a href="https://github.com/untra" target="_blank">@untra</a>.</p>
    </div>

    <nav class="sidebar-nav">
      <a class="sidebar-nav-item" href="/es/">Home</a>

      
      
      
        
        
          
          
        
      
        
        
          
            <a class="sidebar-nav-item" href="/es/about/">Sobre</a>
          
          
        
      
        
        
          
            <a class="sidebar-nav-item" href="/es/una-muy-larga/permalink/">Un muy largo permalink</a>
          
          
        
      
        
        
          
          
        
      
        
        
      
        
        
          
            <a class="sidebar-nav-item" href="/es/sample/">Sample rich text data</a>
          
          
        
      
        
        
          
            <a class="sidebar-nav-item" href="/es/seo/">SEO Recipes</a>
          
          
        
      
        
        
      
        
        
      
        
        
      
        
        
      
        
        
      
        
        
      
        
        
      
        
        
      
        
        
      
        
        
      
        
          
        
          
        
          
        
          
      <a class="sidebar-nav-item" href=""></a>

      <a class="sidebar-nav-item" href="https://rubygems.org/gems/jekyll-polyglot">Ruby Gem</a>
      <a class="sidebar-nav-item" href="https://github.com/untra/polyglot">GitHub project</a>
      <a class="sidebar-nav-item" href="https://github.com/untra/polyglot/tree/master/site/index.html"><small>view this page source on github</small></a>
      <small class="sidebar-nav-item">Currently v1.9.0</small>
    </nav>

    <p><small>&copy; 2025 Samuel Volin</small><br/><small>MIT Licensed</small></p>
<p>
  <!-- jekyll-polyglot will process ferh= into href= through the static_href liquid block tag without relativizing the url; useful for making language navigation switchers  -->
  
<a  href="/" >en</a> •
<a style="font-weight: bold;" href="/es/" >es</a> •
<a  href="/de/" >de</a> •
<a  href="/fr/" >fr</a> •
<a  href="/ru/" >ru</a> •
<a  href="/nl/" >nl</a> •
<a  href="/he/" >he</a> •
<a  href="/ko/" >ko</a> •
<a  href="/zh-CN/" >zh-CN</a> •
<a  href="/pt-BR/" >pt-BR</a>
</p>
  </div>
</div>


    <div class="content container">
      <div class="posts">
  
  <div class="post">
    <h1 class="post-title">
      <a href="/es/2025/01/18/polyglot-1.9.0/">
        Polyglot 1.9.0 - Instructional Improvements
      </a>
    </h1>

    <span class="post-date">18 Jan 2025</span>

    <p>Jekyll-Polyglot 1.9.0 has been released, which has minor dependency updates, and instructional improvements for getting the most from your multi-language website.</p>

<h2 id="community-provided-instructional-improvements">Community provided instructional improvements</h2>

<p>Thank you to <strong><a href="https://github.com/aturret">aturret</a></strong> for helping to maintain the existing <code class="language-plaintext highlighter-rouge">zh-CN</code> site pages. 谢谢！</p>

<p><strong><a href="https://github.com/george-gca">george-gca</a></strong> improved the optional <code class="language-plaintext highlighter-rouge">derive_lang_from_path</code> configuration to better identify document language from the path inference. Tests were added for his helpful <a href="https://github.com/untra/polyglot/pull/222">feature improvement PR</a>. This improvement helps infer the language of posts and pages missing <code class="language-plaintext highlighter-rouge">lang</code> frontmatter, from any part of the document filepath.</p>

<p>Github user <strong><a href="https://github.com/yunseo-kim">yunseo-kim</a></strong> submitted a <a href="https://github.com/untra/polyglot/pull/230">instructions to improve sitemap generation</a> . To help with SEO, a website should have only one root sitemap.xml , and not have duplicates for each sub-language site. Be sure to add the <code class="language-plaintext highlighter-rouge">sitemap.xml</code> to the <code class="language-plaintext highlighter-rouge">exclude_from_localization</code> configuration.</p>

  </div>
  
  <div class="post">
    <h1 class="post-title">
      <a href="/es/2024/08/18/polyglot-1.8.1/">
        Polyglot 1.8.1 - Community Bug Fixes Release
      </a>
    </h1>

    <span class="post-date">18 Aug 2024</span>

    <p>Se ha lanzado Jekyll-Polyglot 1.8.1, que presenta algunas mejoras en las funciones y reconoce errores encontrados por la comunidad y proporciona correcciones.</p>

<h2 id="correcciones-proporcionadas-por-la-comunidad">Correcciones proporcionadas por la comunidad</h2>

<p><strong><a href="https://github.com/hacketiwack">hacketiwack</a></strong> proporcionó una <a href="https://github.com/untra/polyglot/pull/200/files">verificación más estricta para establecer un enlace permanente del documento</a>, evitando problemas posteriores con campos de frontmatter vacíos.</p>

<p>El usuario de Github <strong><a href="https://github.com/blackpill">blackpill</a></strong> envió una <a href="https://github.com/untra/polyglot/pull/211/files">corrección de error de un carácter</a> para la etiqueta de encabezados i18n al renderizar la alternativa href del enlace del idioma predeterminado.</p>

  </div>
  
  <div class="post">
    <h1 class="post-title">
      <a href="/es/2024/03/17/polyglot-1.8.0/">
        Polyglot 1.8.0 - Community Contributions Release
      </a>
    </h1>

    <span class="post-date">17 Mar 2024</span>

    <p>Get excited for Jekyll-Polyglot 1.8.0, which has a few feature improvements and recognizes community documentation and contributions!</p>

<h2 id="language-specific-permalinks">language specific permalinks</h2>

<p>One new feature is to give pages language specific permalinks and to retain their association to other relative pages. This new feature is again improved by <strong><a href="https://github.com/antoniovazquezblanco">antoniovazquezblanco</a></strong>, who is a gentleman and a scholar.</p>

<h2 id="sitemap-generation--i18n-seo">sitemap generation &amp; i18n SEO</h2>

<p>This release also recognizes the quality <a href="https://polyglot.untra.io/sitemap.xml">sitemap.xml</a> and <a href="https://polyglot.untra.io/es/robots.txt">robots.txt</a> solution provided by <strong><a href="https://github.com/jerturowetz">jerturowetz</a></strong>. This website now demonstrates and captures more SEO power by using these to be crawlable as a static jekyll website by search providers. See the example website files <a href="https://github.com/untra/polyglot/tree/master/site">here</a>.</p>

<h2 id="jekyll-polyglot-post_write-hook">jekyll :polyglot :post_write hook</h2>

<p>Github user <strong><a href="https://github.com/obfusk">obfusk</a></strong> contributed a <a href="https://github.com/untra/polyglot/pull/142">tiny PR</a> a few years back:</p>

<p>With polyglot <code class="language-plaintext highlighter-rouge">:site, :post_write</code> like these run for each child processes:</p>

<div class="language-rb highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="no">Jekyll</span><span class="o">::</span><span class="no">Hooks</span><span class="p">.</span><span class="nf">register</span> <span class="ss">:site</span><span class="p">,</span> <span class="ss">:post_write</span> <span class="k">do</span> <span class="o">|</span><span class="n">site</span><span class="o">|</span>
  <span class="o">...</span>
<span class="k">end</span>
</code></pre></div></div>

<p>This release adds a custom <code class="language-plaintext highlighter-rouge">:post_write</code> hook that runs exactly once, after all languages been processed (whether or not <code class="language-plaintext highlighter-rouge">parallel_localization</code> is used):</p>

<div class="language-rb highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="no">Jekyll</span><span class="o">::</span><span class="no">Hooks</span><span class="p">.</span><span class="nf">register</span> <span class="ss">:polyglot</span><span class="p">,</span> <span class="ss">:post_write</span> <span class="k">do</span> <span class="o">|</span><span class="n">site</span><span class="o">|</span>
  <span class="c1"># do something amazing here!</span>
<span class="k">end</span>
</code></pre></div></div>

<p>This feature is helpful for complex jekyll static sites that make additional use of <a href="https://jekyllrb.com/docs/plugins/hooks/">jekyll hook plugins</a>.</p>

<p>She also contributed a fix for <a href="https://github.com/untra/polyglot/pull/145">additional logging when language subprocesses crash</a>. Thanks for this contribution!</p>

<h2 id="localized-variables-and-portuguese-translation">localized variables and portuguese translation.</h2>

<p><strong><a href="https://github.com/george-gca">george-gca</a></strong> is a talented and awesome guy, contributing <a href="/es/2024/02/29/localized-variables/">an entire blogpost</a> on how best to localize rich text from site data. He also provided a <a href="https://polyglot.untra.io/pt-BR/">site brazilian translation</a>.</p>


  </div>
  
  <div class="post">
    <h1 class="post-title">
      <a href="/es/2024/02/29/localized-variables/">
        Localized variables
      </a>
    </h1>

    <span class="post-date">29 Feb 2024</span>

    <p>Polyglot allows you to have different pages for different languages in your Jekyll site. For example, one could have a page <code class="language-plaintext highlighter-rouge">about.md</code> in English and another <code class="language-plaintext highlighter-rouge">about.md</code> in Spanish with completely different layouts. But if you want to have the same layout for both pages, you can use localized variables. This is a way to have different data for different languages in your Jekyll site, but using the same layout for all languages.</p>

<p>As an example I will use a <a href="https://github.com/george-gca/multi-language-al-folio">template site</a> created with Polyglot.</p>

<h2 id="sharing-a-layout-between-pages">Sharing a layout between pages</h2>

<p>In that site they have an about page for every language, in their case english in <a href="https://github.com/george-gca/multi-language-al-folio/blob/main/_pages/en-us/about.md">_pages/en-us/about.md</a> and brazilian portuguese in <a href="https://github.com/george-gca/multi-language-al-folio/blob/main/_pages/pt-br/about.md">_pages/pt-br/about.md</a>. In both pages we can see that they have the same keys in the frontmatter, but some with different values. Both files point to the same <a href="https://jekyllrb.com/docs/layouts/">layout</a>, <a href="https://github.com/george-gca/multi-language-al-folio/blob/main/_layouts/about.liquid">about</a>, and this layout uses the values in the frontmatter to render the page.</p>

<p>For example, the <code class="language-plaintext highlighter-rouge">subtitle</code> key in the english page has the value <code class="language-plaintext highlighter-rouge">subtitle: &lt;a href='#'&gt;Affiliations&lt;/a&gt;. Address. Contacts. Moto. Etc.</code> and in the brazilian portuguese page it has <code class="language-plaintext highlighter-rouge">subtitle: &lt;a href='#'&gt;Afiliações&lt;/a&gt;. Endereço. Contatos. Lema. Etc.</code>. To use this information in the layout, it is used like this:</p>

<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="cp">{{</span><span class="w"> </span><span class="nv">page</span><span class="p">.</span><span class="nv">subtitle</span><span class="w"> </span><span class="cp">}}</span>
</code></pre></div></div>

<p>The same goes for the content below the frontmatter in both files, which is simply used in the layout like this:</p>

<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="cp">{{</span><span class="w"> </span><span class="nv">content</span><span class="w"> </span><span class="cp">}}</span>
</code></pre></div></div>

<p>Polyglot will automatically render the page with the correct values for the current language.</p>

<h2 id="sharing-a-layout-between-pages-with-localized-data">Sharing a layout between pages with localized data</h2>

<p>For the <code class="language-plaintext highlighter-rouge">subtitle</code> of the page they used <code class="language-plaintext highlighter-rouge">key: value</code> pairs in the frontmatter, but sometimes we want to use these same pairs in different parts of the site. For example, if we want to use the same <code class="language-plaintext highlighter-rouge">subtitle</code> in the <code class="language-plaintext highlighter-rouge">about.md</code> and in another page, we would have to repeat the same pair in the frontmatter of both pages. This is not ideal because if we want to change the <code class="language-plaintext highlighter-rouge">subtitle</code> we would have to change it in two places. This is where localized data comes in. You can create a file like <code class="language-plaintext highlighter-rouge">_data/:lang/strings.yml</code>, one for each language, and Polyglot will bring those keys under <code class="language-plaintext highlighter-rouge">site.data[:lang].strings</code>.</p>

<p>For example, in the template site there are two files, <a href="https://github.com/george-gca/multi-language-al-folio/blob/main/_data/en-us/strings.yml">_data/en-us/strings.yml</a> and <a href="https://github.com/george-gca/multi-language-al-folio/blob/main/_data/pt-br/strings.yml">_data/pt-br/strings.yml</a>. In the first file they have:</p>

<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">latest_posts</span><span class="pi">:</span> <span class="s">latest posts</span>
</code></pre></div></div>

<p>And in the second file they have:</p>

<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">latest_posts</span><span class="pi">:</span> <span class="s">últimas postagens</span>
</code></pre></div></div>

<p>This way, they can use the <code class="language-plaintext highlighter-rouge">latest_posts</code> key in the layout like this:</p>

<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="cp">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">data</span><span class="p">[</span><span class="nv">site</span><span class="p">.</span><span class="nv">active_lang</span><span class="p">].</span><span class="nv">strings</span><span class="p">.</span><span class="nv">latest_posts</span><span class="w"> </span><span class="cp">}}</span>
</code></pre></div></div>

<p>Which will correctly get the value for the <code class="language-plaintext highlighter-rouge">latest_posts</code> variable defined in the file <code class="language-plaintext highlighter-rouge">_data/:lang/strings.yml</code> for the current language.</p>

<h2 id="defining-which-variable-to-use-in-the-frontmatter">Defining which variable to use in the frontmatter</h2>

<p>Now if you want to define this variable in the frontmatter of the page, this gets a little bit trickier. One possible solution is to check if the value of the variable has a <code class="language-plaintext highlighter-rouge">.</code> in it, and if it does use the value in the file <code class="language-plaintext highlighter-rouge">_data/:lang/strings.yml</code>. This is how you would do it:</p>

<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="cp">{%</span><span class="w"> </span><span class="nt">if</span><span class="w"> </span><span class="nv">frontmatter_var</span><span class="w"> </span><span class="ow">contains</span><span class="w"> </span><span class="s1">'.'</span><span class="w"> </span><span class="cp">%}</span>
  <span class="cp">{%</span><span class="w"> </span><span class="nt">assign</span><span class="w"> </span><span class="nv">first_part</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">frontmatter_var</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">split</span><span class="p">:</span><span class="w"> </span><span class="s1">'.'</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">first</span><span class="w"> </span><span class="cp">%}</span>
  <span class="cp">{%</span><span class="w"> </span><span class="nt">assign</span><span class="w"> </span><span class="nv">last_part</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">frontmatter_var</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">split</span><span class="p">:</span><span class="w"> </span><span class="s1">'.'</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">last</span><span class="w"> </span><span class="cp">%}</span>
  <span class="cp">{%</span><span class="w"> </span><span class="nt">capture</span><span class="w"> </span><span class="nv">result</span><span class="w"> </span><span class="cp">%}{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">data</span><span class="p">[</span><span class="nv">site</span><span class="p">.</span><span class="nv">active_lang</span><span class="p">].</span><span class="nv">strings</span><span class="p">[</span><span class="nv">first_part</span><span class="p">][</span><span class="nv">last_part</span><span class="p">]</span><span class="w"> </span><span class="cp">}}{%</span><span class="w"> </span><span class="nt">endcapture</span><span class="w"> </span><span class="cp">%}</span>
<span class="cp">{%</span><span class="w"> </span><span class="nt">endif</span><span class="w"> </span><span class="cp">%}</span>

<span class="cp">{{</span><span class="w"> </span><span class="nv">result</span><span class="w"> </span><span class="cp">}}</span>
</code></pre></div></div>

<p>This will work, for example, if <code class="language-plaintext highlighter-rouge">frontmatter_var = blog.title</code>.</p>

<p>Now, if you need to check if the localization string (in this case <code class="language-plaintext highlighter-rouge">blog.title</code>) actually exists in the file <code class="language-plaintext highlighter-rouge">_data/:lang/strings.yml</code> before using it, you’ll have to create a plugin to check if the variable exists in the file <code class="language-plaintext highlighter-rouge">_data/:lang/strings.yml</code> and if it does, use it, otherwise fallback to any value you want. I will not go into detail on how to do this, but I will show you how to use it. You can see the code for the plugin <a href="https://github.com/george-gca/multi-language-al-folio/blob/main/_plugins/localization-exists.rb">here</a>.</p>

<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="cp">{%</span><span class="w"> </span><span class="nt">if</span><span class="w"> </span><span class="nv">frontmatter_var</span><span class="w"> </span><span class="ow">contains</span><span class="w"> </span><span class="s1">'.'</span><span class="w"> </span><span class="cp">%}</span>
  <span class="cp">{%</span><span class="w"> </span><span class="nt">capture</span><span class="w"> </span><span class="nv">contains_localization</span><span class="w"> </span><span class="cp">%}{%</span><span class="w"> </span><span class="nt">localization_exists</span><span class="w"> </span><span class="cp">{{</span><span class="w"> </span><span class="nv">frontmatter_var</span><span class="w"> </span><span class="cp">}}</span><span class="w"> </span><span class="cp">%}{%</span><span class="w"> </span><span class="nt">endcapture</span><span class="w"> </span><span class="cp">%}</span>
  <span class="cp">{%</span><span class="w"> </span><span class="nt">if</span><span class="w"> </span><span class="nv">contains_localization</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="s1">'true'</span><span class="w"> </span><span class="cp">%}</span>
    <span class="cp">{%</span><span class="w"> </span><span class="nt">assign</span><span class="w"> </span><span class="nv">first_part</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">frontmatter_var</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">split</span><span class="p">:</span><span class="w"> </span><span class="s1">'.'</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">first</span><span class="w"> </span><span class="cp">%}</span>
    <span class="cp">{%</span><span class="w"> </span><span class="nt">assign</span><span class="w"> </span><span class="nv">last_part</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">frontmatter_var</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">split</span><span class="p">:</span><span class="w"> </span><span class="s1">'.'</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">last</span><span class="w"> </span><span class="cp">%}</span>
    <span class="cp">{%</span><span class="w"> </span><span class="nt">capture</span><span class="w"> </span><span class="nv">result</span><span class="w"> </span><span class="cp">%}{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">data</span><span class="p">[</span><span class="nv">site</span><span class="p">.</span><span class="nv">active_lang</span><span class="p">].</span><span class="nv">strings</span><span class="p">[</span><span class="nv">first_part</span><span class="p">][</span><span class="nv">last_part</span><span class="p">]</span><span class="w"> </span><span class="cp">}}{%</span><span class="w"> </span><span class="nt">endcapture</span><span class="w"> </span><span class="cp">%}</span>
  <span class="cp">{%</span><span class="w"> </span><span class="nt">else</span><span class="w"> </span><span class="cp">%}</span>
    <span class="cp">{%</span><span class="w"> </span><span class="nt">capture</span><span class="w"> </span><span class="nv">result</span><span class="w"> </span><span class="cp">%}</span>fallback value<span class="cp">{%</span><span class="w"> </span><span class="nt">endcapture</span><span class="w"> </span><span class="cp">%}</span>
  <span class="cp">{%</span><span class="w"> </span><span class="nt">endif</span><span class="w"> </span><span class="cp">%}</span>
<span class="cp">{%</span><span class="w"> </span><span class="nt">endif</span><span class="w"> </span><span class="cp">%}</span>

<span class="cp">{{</span><span class="w"> </span><span class="nv">result</span><span class="w"> </span><span class="cp">}}</span>
</code></pre></div></div>

  </div>
  
  <div class="post">
    <h1 class="post-title">
      <a href="/es/2023/10/29/polyglot-1.7.0/">
        Polyglot 1.7.0 y portada `page_id` para diferentes enlaces permanentes por idioma
      </a>
    </h1>

    <span class="post-date">29 Oct 2023</span>

    <p>Me complace anunciar Jekyll-Polyglot 1.7.0, que tiene una nueva función para proporcionar a las páginas enlaces permanentes específicos del idioma y conservar su asociación con otras páginas relativas.</p>

<p>Esta nueva característica es proporcionada por <strong><a href="https://github.com/antoniovazquezblanco">antoniovazquezblanco</a></strong>, que es un apuesto caballero y un erudito.</p>

<h2 id="use-el-frontmatter-page_id-para-asociar-páginas-con-diferentes-enlaces-permanentes">use el frontmatter <code class="language-plaintext highlighter-rouge">page_id</code> para asociar páginas con diferentes enlaces permanentes</h2>

<p>Polyglot asocia páginas haciendo coincidir sus enlaces permanentes o nombres de archivos. Sin embargo, es posible que algunas traducciones de sitios prefieran páginas con enlaces permanentes únicos.</p>

<p>Polyglot ya coordina múltiples copias del mismo documento en diferentes idiomas. Por lo tanto, cerrar una propiedad diferente como <code class="language-plaintext highlighter-rouge">page_id</code> no es diferente a cerrar el enlace permanente.</p>

<p>El uso de un <code class="language-plaintext highlighter-rouge">page_id</code> para coordinar páginas similares con diferentes enlaces permanentes garantiza que los enlaces permanentes personalizados aún se puedan ver en sitios de idiomas específicos.</p>

<h3 id="redirecciones-para-enlaces-permanentes-únicos">redirecciones para enlaces permanentes únicos</h3>

<p>El desafío con los enlaces permanentes únicos viene con relativizar esas URL. Polyglot evita este problema por completo sugiriendo enlaces permanentes consistentes.</p>

<p>Para ayudar con esto, conjuntos políglotas <code class="language-plaintext highlighter-rouge">redirect_from</code> portada oculta en estas páginas, enumerando los enlaces permanentes únicos de las páginas correspondientes.</p>

<p>Cuando se utiliza el complemento <code class="language-plaintext highlighter-rouge">jekyll-redirect-from</code>, se recogerá esa información frontal y se realizarán redireccionamientos inteligentes al enlace permanente personalizado de la página.</p>

<p>Para ver esto en acción, visite <a href="/es/a-really-long/permalink/">esta página con un enlace permanente largo en diferentes idiomas</a>.</p>

<h2 id="otras-correcciones-de-errores">Otras correcciones de errores</h2>

<ul>
  <li>Esta versión debería tener una solución para <a href="https://github.com/untra/polyglot/issues/151">#151</a> y <a href="https://github.com/untra/polyglot/issues/184">#184</a>, evitando fallas en el inicio al llamar a otros comandos jekyll.</li>
</ul>

  </div>
  
</div>

<div class="pagination">
  
    <a class="pagination-item older" href="/es/page2">Older</a>
  
  
    <span class="pagination-item newer">Newer</span>
  
</div>

    </div>

  </body>
  <script async src="https://www.googletagmanager.com/gtag/js?id=G-HWC3D32MT8"></script>
  <script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());
  
    gtag('config', 'G-HWC3D32MT8');
  </script>
</html>