Latest translations

textpattern/lang/cs.ini

@@ -473,7 +473,7 @@ viewsite="Zobrazit"
 website="Webová stránka"
 width="Šířka"
 with_selected="Výběr"
-with_selected_option="S {count} označenými…"
+with_selected_option="(vybráno: {count}) s označenými…"
 yes="Ano"
 [css]
 all_stylesheets="Všechny styly"

textpattern/lang/en-gb_pophelp.xml

@@ -618,18 +618,14 @@
 <p>In addition to the standard form template types (article, file, misc, etc.), Publishers can define custom types. The purpose of custom form template types is twofold: easier form template classification and custom asset definitions.</p>
 <p>The format of the preference is <a rel="external" target="_blank" href="https://en.wikipedia.org/wiki/INI_file">INI <span class="ui-icon ui-icon-extlink">(opens an external link in a new window)</span></a>, with each section corresponding to a form template type.</p>
 <p>To define a custom form type (e.g. <code>js</code>) one must append (on a separate line) a <code>[js]</code> section. A default title can be set via a <code>title="Javascript"</code> entry in the corresponding section. If needed, localised titles can be appended too (e.g. <code>ru="Скрипт"</code>).</p>
-<p>Additionally, a form template <a rel="external" target="_blank" href="https://www.iana.org/assignments/media-types/media-types.xhtml">media type <span class="ui-icon ui-icon-extlink">(opens an external link in a new window)</span></a> (formerly known as a MIME type) can be specified, e.g. <code>mediatype="application/javascript"</code>. This turns form templates of this type into custom assets that can be served as the set media type, either from the database or from disk (flat files) via the <code>&lt;txp:output_form /&gt;</code> tag. For example, a form template named <code>myscript.js</code> of <code>[js]</code> type with a media type of <code>mediatype="application/javascript"</code> can be included via a HTML <code>&lt;script&gt;</code> tag in your code like so:</p>
-<pre><code>&lt;script&gt;
-    &lt;txp:output_form form="myscript.js"
-    format="flat.script" /&gt;
-&lt;/script&gt;</code></pre>
+<p>Additionally, a form template <a rel="external" target="_blank" href="https://www.iana.org/assignments/media-types/media-types.xhtml">media type <span class="ui-icon ui-icon-extlink">(opens an external link in a new window)</span></a> (formerly known as a MIME type) can be specified, e.g. <code>mediatype="application/javascript"</code>. This turns form templates of this type into custom assets that can be served as the set media type, either from the database or from disk (flat files) via the <code>&lt;txp:output_form /&gt;</code> tag. For example, a form template named <code>myscript.js</code> of <code>[js]</code> type with a media type of <code>application/javascript</code> can be included in your code like so:</p>
+<pre><code>&lt;txp:output_form form="myscript.js"
+    format="flat.script" /&gt;</code></pre>
+<p>This will generate the following HTML <code>&lt;script&gt;</code> tag:<p>
+<pre><code>&lt;script src="path/to/flat/myscript.js"&gt;&lt;/script&gt;</code></pre>
 <p>Only form templates with the name extension corresponding to their type (e.g. <code>myscript.js</code>) can be served as flat files. In this case, they will not be processed by Textpattern at all and are accessible via their URL.</p>
-If a form template needs processing (if it contains Textpattern tags), you must serve it from the database like so:</p>
-<pre><code>&lt;script&gt;
-    &lt;txp:txp:output_form form="myscript.js"
-    format="script" /&gt;
-&lt;/script&gt;</code></pre>
-<p>In this case you shouldn’t add the extension to the form name - call it just <code>myscript</code> (without <code>.js</code>) to make it inaccessible via a standard URL.</p>
+If a form template needs processing (if it contains Textpattern tags), you must serve it from the database. In this case you shouldn’t add the extension to the form name - call it just <code>myscript</code> (without <code>.js</code>) to make it inaccessible via a standard URL - and include it like so:</p>
+<pre><code>&lt;txp::myscript format="script" /&gt;</code></pre>
         ]]></item>
         <item id="custom_overview" title="Custom fields"><![CDATA[
 <h2>Custom fields</h2>

textpattern/lang/en-us_pophelp.xml

@@ -618,18 +618,14 @@
 <p>In addition to the standard form template types (article, file, misc, etc.), Publishers can define custom types. The purpose of custom form template types is twofold: easier form template classification and custom asset definitions.</p>
 <p>The format of the preference is <a rel="external" target="_blank" href="https://en.wikipedia.org/wiki/INI_file">INI <span class="ui-icon ui-icon-extlink">(opens an external link in a new window)</span></a>, with each section corresponding to a form template type.</p>
 <p>To define a custom form type (e.g. <code>js</code>) one must append (on a separate line) a <code>[js]</code> section. A default title can be set via a <code>title="Javascript"</code> entry in the corresponding section. If needed, localized titles can be appended too (e.g. <code>ru="Скрипт"</code>).</p>
-<p>Additionally, a form template <a rel="external" target="_blank" href="https://www.iana.org/assignments/media-types/media-types.xhtml">media type <span class="ui-icon ui-icon-extlink">(opens an external link in a new window)</span></a> (formerly known as a MIME type) can be specified, e.g. <code>mediatype="application/javascript"</code>. This turns form templates of this type into custom assets that can be served as the set media type, either from the database or from disk (flat files) via the <code>&lt;txp:output_form /&gt;</code> tag. For example, a form template named <code>myscript.js</code> of <code>[js]</code> type with a media type of <code>mediatype="application/javascript"</code> can be included via a HTML <code>&lt;script&gt;</code> tag in your code like so:</p>
-<pre><code>&lt;script&gt;
-    &lt;txp:output_form form="myscript.js"
-    format="flat.script" /&gt;
-&lt;/script&gt;</code></pre>
+<p>Additionally, a form template <a rel="external" target="_blank" href="https://www.iana.org/assignments/media-types/media-types.xhtml">media type <span class="ui-icon ui-icon-extlink">(opens an external link in a new window)</span></a> (formerly known as a MIME type) can be specified, e.g. <code>mediatype="application/javascript"</code>. This turns form templates of this type into custom assets that can be served as the set media type, either from the database or from disk (flat files) via the <code>&lt;txp:output_form /&gt;</code> tag. For example, a form template named <code>myscript.js</code> of <code>[js]</code> type with a media type of <code>application/javascript</code> can be included in your code like so:</p>
+<pre><code>&lt;txp:output_form form="myscript.js"
+    format="flat.script" /&gt;</code></pre>
+<p>This will generate the following HTML <code>&lt;script&gt;</code> tag:<p>
+<pre><code>&lt;script src="path/to/flat/myscript.js"&gt;&lt;/script&gt;</code></pre>
 <p>Only form templates with the name extension corresponding to their type (e.g. <code>myscript.js</code>) can be served as flat files. In this case, they will not be processed by Textpattern at all and are accessible via their URL.</p>
-If a form template needs processing (if it contains Textpattern tags), you must serve it from the database like so:</p>
-<pre><code>&lt;script&gt;
-    &lt;txp:txp:output_form form="myscript.js"
-    format="script" /&gt;
-&lt;/script&gt;</code></pre>
-<p>In this case you shouldn’t add the extension to the form name - call it just <code>myscript</code> (without <code>.js</code>) to make it inaccessible via a standard URL.</p>
+If a form template needs processing (if it contains Textpattern tags), you must serve it from the database. In this case you shouldn’t add the extension to the form name - call it just <code>myscript</code> (without <code>.js</code>) to make it inaccessible via a standard URL - and include it like so:</p>
+<pre><code>&lt;txp::myscript format="script" /&gt;</code></pre>
         ]]></item>
         <item id="custom_overview" title="Custom fields"><![CDATA[
 <h2>Custom fields</h2>

textpattern/lang/hu.ini

@@ -4,6 +4,7 @@ lang_code="hu"
 lang_dir="ltr"
 [admin]
 account_activation="Kérjük, aktiválja a fiókját"
+account_activation_confirmation="Az alábbi link segítségével aktiválja fiókját, és hozzon létre egy jelszót."
 changeprivilege="Jogosultság megváltoztatása"
 change_email_address="Email címed megváltoztatása"
 change_password="Jelszavad megváltoztatása"
@@ -17,6 +18,7 @@ edit_author="Szerző szerkesztése <strong>{name}</strong>"
 email_changed="Az email cím megváltozott a következőre: <strong>{email}</strong>"
 error_adding_new_author="Hiba az új szerző hozzáadásakor"
 freelancer="Szabadúszó"
+invalid_token="Jelszó visszaállítása biztonsági token érvénytelen."
 last_login="Utoljára belépve"
 login_name="Belépés"
 log_in_at="Belépve"
@@ -373,7 +375,6 @@ viewsite="Oldal megtekintése"
 website="Weblap"
 width="Szélesség"
 with_selected="A kiválasztottak:"
-with_selected_option="A kiválasztottak:"
 yes="Igen"
 [css]
 all_stylesheets="Stíluslapok"

textpattern/setup/lang/hu.ini

@@ -4,6 +4,7 @@ lang_code="hu"
 lang_dir="ltr"
 [setup]
 about_to_create="Most tudod létrehozni és feltölteni az adatbázis táblákat."
+add_config_file="Config fájl hozzáadása"
 already_installed="Úgy fest, a Textpattern már installálva van. Ha egy tiszta szerkezetet szeretnél, kérlek töröld a <code>config.php</code> nevű állományt a <code>{configpath}</code> könyvtárból és próbáld újra."
 back="Vissza"
 before_you_proceed="Mielőtt tovább mennél:"