<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>PVlt Localization</title><link>https://gallery.orchardproject.net:443/Packages/Pvlt.Localization</link><description>&lt;h2&gt;Culture Picker Widget&lt;/h2&gt;

&lt;p&gt;The culture picker widget provides links for each supported culture as configured in site's settings.&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;&lt;img src="/Media/Default/Users/pvlt/Screens/Culture%20Picker%20Widget%201.png" alt="Standard front-end design for the culture picker" /&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It constructs links as described here:&lt;/p&gt;

&lt;p&gt;First it tries to retrieve the related translation of the currently displayed content item . If it doesn't exists, it tries to retrieve the related translation of the home page. If a translated home page doesn't exists, it finaly provide a "#" and the link is desactivated.&lt;/p&gt;

&lt;p&gt;If nothing is displayed, that means that there is a critical error. You can inspect the page's html code to read a hidden "log" message that can help you to resolve the problem. Usually there's a content management problem.&lt;/p&gt;

&lt;h2&gt;Translation management&lt;/h2&gt;

&lt;p&gt;To help you to keep a well organized content that is resilient to a culture setting change, the first culture that you are allowed to select is the site's default culture. With that rule, the the first translation of a content item will be always in default culture.&lt;/p&gt;

&lt;p&gt;For the next translations, the module selects the "default culture" related translation as the "master content item" and you can select all other cultures.&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;&lt;img src="/Media/Default/Users/pvlt/Screens/Untranslated%20Content.png" alt="An untranslated content can only register the default site culture" /&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;When you translate a content item, some parts of the master content item are cloned (Title, Body, Layout). So you don't have to spend time to reimplement a common structure, you just replace the text to translate.&lt;/p&gt;

&lt;h2&gt;SEO Optimization&lt;/h2&gt;

&lt;p&gt;The standard localization part template is overridden to inject tags "&amp;lt;link rel="alternate" hreflang="es" href="http://es.example.com/" /&amp;gt;" into the &amp;lt;head&amp;gt; of the page (like google advises it).&lt;/p&gt;
</description><item><title>PVlt Localization 1.1</title><link>https://gallery.orchardproject.net:443/Packages/Pvlt.Localization/1.1</link><description>&lt;ul&gt;
&lt;li&gt;[Bug] Fix for culture selection after an invalid post.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Sun, 08 Jan 2017 10:37:09 GMT</pubDate><guid isPermaLink="true">https://gallery.orchardproject.net:443/Packages/Pvlt.Localization/1.1</guid></item><item><title>PVlt Localization 1.0</title><link>https://gallery.orchardproject.net:443/Packages/Pvlt.Localization/1.0</link><description>PVlt Localization 1.0</description><pubDate>Tue, 04 Oct 2016 10:18:16 GMT</pubDate><guid isPermaLink="true">https://gallery.orchardproject.net:443/Packages/Pvlt.Localization/1.0</guid></item><item><title>PVlt Localization 0.8</title><link>https://gallery.orchardproject.net:443/Packages/Pvlt.Localization/0.8</link><description>PVlt Localization 0.8</description><pubDate>Sun, 19 Jun 2016 09:23:07 GMT</pubDate><guid isPermaLink="true">https://gallery.orchardproject.net:443/Packages/Pvlt.Localization/0.8</guid></item></channel></rss>