Merge remote-tracking branch 'cibernox/main' into merge-from-upstream-main

Author: tomoam

.netlify/functions-internal/__render.js

@@ -95005,8 +95005,8 @@ var Configuration = create_ssr_component(($$result, $$props, $$bindings, slots)
 ${validate_component(Codeblock, "Codeblock").$$render($$result, { lang: "html" }, {}, {
     default: () => `${escape(`<script context="module">
 	import { addMessages, init } from 'svelte-intl-precompile';
-	import en from '$locales/en.js';
-	import es from '$locales/es.js';
+	import en from '$locales/en';
+	import es from '$locales/es';
 	addMessages('en', en);
 	addMessages('es', es);
 	init({

locales/en.json

@@ -27,11 +27,11 @@
   "icu-crash-course.table-heads.definition": "Entry",
   "icu-crash-course.table-heads.values": "Values",
   "icu-crash-course.table-heads.output": "Output",
-  "icu-crash-course.paragraph.main-1": "This library analyzes and compiles the translations authored in the ICU message syntax. While the ICU message syntax is an independent proyect this is an accelerated course on why it's good and how to use the main features.",
+  "icu-crash-course.paragraph.main-1": "This library analyzes and compiles the translations authored in the ICU message syntax. While the ICU message syntax is an independent project this is an accelerated course on why it's good and how to use the main features.",
   "icu-crash-course.subsection.why": "Why use the ICU message syntax?",
   "icu-crash-course.paragraph.why-1": "ICU stands for <em class='italic'>International Components for Unicode</em>. While its popularity begun in C/C++ and Java, it's the javascript ecosystem where it has become the defacto standard for internationalization, although it's also popular in Python and PHP.",
   "icu-crash-course.paragraph.why-2": "Internationalizing apps is a whole lot more than just mapping some keys to the appropriate translated string in a dictionary. Properly internationalized apps must handle all aspects of translation, including the way dates and times are formatted, what delimiters are used in numbers to separate the thousands or the decimals, currencies and support gendered languages.",
-  "icu-crash-course.paragraph.why-3": "Even something as simple as plurals can get very complex depending on the language. English, German and Spanish have singular and plural, but some slavic languages have 3, and other languages like Arabic have 6 depending on the number of items being pluralized. Sometimes the threshold where we have to change from one plural form to the next varies depending on the reginal variant. <br> English doesn't have many gendered words but French or Italian do, and the adjectives must match the noun's gender. Formatting <code class='inline'>123456789</code> in the US english variant will result in <code class='inline'>123,456,789</code> but in the Indian variant will be <code class='inline'>12,34,56,789</code>. <br> Formatting currencies the $ symbol goes before the amount, but the € goes after.",
+  "icu-crash-course.paragraph.why-3": "Even something as simple as plurals can get very complex depending on the language. English, German and Spanish have singular and plural, but some slavic languages have 3, and other languages like Arabic have 6 depending on the number of items being pluralized. Sometimes the threshold where we have to change from one plural form to the next varies depending on the regional variant. <br> English doesn't have many gendered words but French or Italian do, and the adjectives must match the noun's gender. Formatting <code class='inline'>123456789</code> in the US english variant will result in <code class='inline'>123,456,789</code> but in the Indian variant will be <code class='inline'>12,34,56,789</code>. <br> Formatting currencies the $ symbol goes before the amount, but the € goes after.",
   "icu-crash-course.paragraph.why-4": "The ICU syntax abstracts all this complexity from the developers and gives the real professional translators a meta language expressive enough to handle all the subtleties on they side.",
   "icu-crash-course.subsection.interpolations": "Interpolations",
   "icu-crash-course.paragraph.interpolations-1": "ICU messages support interpolating values, which will be properly sanitized so passing <code class='inline'>undefined</code> will not interpolate as <em class='italic'>\"undefined\"</em>.",
@@ -79,7 +79,13 @@
   "getting-started.paragraph.create-translations-1": "Next create a folder to put your translations files in. I like to use {dir1} {or} {dir2}",
   "getting-started.paragraph.create-translations-2": "at the root of the project, but really any folder will do.",
   "getting-started.paragraph.create-translations-3": "I recommend using JSON files but you can use use javascript with an object as their default export. Whatever the file extension, you translations inside are just regular strings in the ICU message syntax:",
-  "getting-started.paragraph.create-translations-4": "I prefer shallow dictionaries like the one above, but you can also define translations using nested dictionaries.",
+  "getting-started.paragraph.create-translations-4": "I prefer when the dictionary has a single level and using dots to create hierarchies like in the one above, but you can also nest objects like in the next example:",
+  "getting-started.paragraph.create-translations-5": "JSON is too constrained! I want more flexibility!",
+  "getting-started.paragraph.create-translations-6": "You can also use JSON 5 features in your json files. That is, you can have comments, multi-line strings, single quotes, trailing commas... <br>It just works out of the box.",
+  "getting-started.paragraph.create-translations-7": "I don't like curly braces",
+  "getting-started.paragraph.create-translations-8": "Fair enough. If you like significant whitespace you can also use YAML files. Just use the .yaml or .yml extension names. If you are into that sort of things.",
+  "getting-started.paragraph.create-translations-9": "I want even more features",
+  "getting-started.paragraph.create-translations-10": "You can also define your translation in .js files, .ts files and .mjs files. Your module must export the object with the translations as its default export.",
   "getting-started.subsection.hook-into-sveltekit": "Hook the compiler into SvelteKit",
   "getting-started.paragraph.hook-into-sveltekit-1": "This library's build time compiler needs to hook into the build pipeline of your app. For that, add it to the list of vite plugins in your <code class=\"bg-code px-2\">{path}</code>",
   "getting-started.paragraph.hook-into-sveltekit-2": "You are set, time to use the library.",
@@ -123,7 +129,7 @@
   "configuration.definitions.path": "Extracts the locale from the path of the URL.<br>E.g <pre class='inline'>getLocaleFromPathname(/^\/((es|en)(-\\w\\w)?)/)</pre> for <pre class='inline'>myapp.com/en-US/users</pre>",
   "configuration.definitions.host": "Extracts the locale from host.<br>E.g <pre class='inline'>getLocaleFromHostname(/^((es|en)(-\\w\\w)?)\\./)</pre> for <pre class='inline'>https://pt.myapp.com</pre>",
   "configuration.subsection.custom-formats": "Custom formats",
-  "configuration.paragraph.custom-formats-1": "This library can format numbers, dates and times. It does it without adding significant weight to your app by leverating the Intl API already present in all modern browsers and in Node.js.<br/>By default you app can use these formats, but you can add your own.",
+  "configuration.paragraph.custom-formats-1": "This library can format numbers, dates and times. It does it without adding significant weight to your app by leveraging the Intl API already present in all modern browsers and in Node.js.<br/>By default you app can use these formats, but you can add your own.",
   "configuration.paragraph.custom-formats-2": "If you want to define your own formats pass them on initialization using the",
   "configuration.paragraph.custom-formats-3": "option, which will be deep merged with the default formats listed above. The formats must be valid options to forward to",
 

locales/es.json

@@ -79,6 +79,12 @@
   "getting-started.paragraph.create-translations-2": "en la raiz del proyecto, pero en realidad puedes colocar el directorio donde tu prefieras",
   "getting-started.paragraph.create-translations-3": "Recomiendo usar ficheros .json pero puedes también crear ficheros javascript que exporten un único objeto que contiene las traducciones. Cualquiera que sea tu preferencia, las traducciones son simples cadenas con la sintaxis ICU:",
   "getting-started.paragraph.create-translations-4": "Yo prefiero el diccionario de traducciones tenga un único nivel y usar puntos para crear jerarquías como el de arriba, pero también puedes anidar objectos como a continuación:",
+  "getting-started.paragraph.create-translations-5": "¡JSON es demasido rígido! ¡Quiero más flexibilidad!",
+  "getting-started.paragraph.create-translations-6": "Puedes usar funcionalidades de JSON 5 en tus ficheros json. Por ejemplo, puedes usar comentarios, strings multi-línea, comillas simples, comas al final de línas... <br>Funciona automáticamente.",
+  "getting-started.paragraph.create-translations-7": "No me gustan las llaves",
+  "getting-started.paragraph.create-translations-8": "Como quieras. Si te gusta usar espacios puede puedes tambien utilizar ficheros YAML. Tan solo añade la extensión .yaml o .yml. Si es que te van esas cosas.",
+  "getting-started.paragraph.create-translations-9": "Quiero más funcionalidades",
+  "getting-started.paragraph.create-translations-10": "Puedes definir tus traducciones en ficheros .js, ficheros .ts y ficheros .mjs. El módulo debe exportar un objeto con las traducciones como su export por defecto.",
   "getting-started.subsection.hook-into-sveltekit": "Acomplar el compilador a SvelteKit",
   "getting-started.paragraph.hook-into-sveltekit-1": "El compilador de esta librería necesita integrarse en el proceso de complilado de SvelteKit de tu proyecto. Para ello añadelo a las lista de plugins de vite en tu <code class=\"bg-code px-2\">{path}</code>",
   "getting-started.paragraph.hook-into-sveltekit-2": "Y ya está todo listo. Tiempo de usar la librería.",

locales/gl.json

@@ -4,7 +4,6 @@
   "main.title": "Svelte Intl Precompile",
   "main.subtitle": "A librería de i18n para Svelte que analiza e transforma as túas traduccións en tempo de compilación.",
   "playground.title": "Playground",
-  
   "introduction.title": "Introducción",
   "introduction.subsection.why-use-it": "¿Por qué querería usala?",
   "introduction.paragraph.why-use-it-1": "Svelte-intl-precompile é unha librería de i18n para apps Svelte que busca proporcionar todas as funcionalidades ca túa app pode precisar co mínimo impacto tanto no tamaño da túa app como na súa velocidade de execución",
@@ -22,7 +21,6 @@
   "introduction.list-items.features-3": "Unha API deseñada para Svelte.js que poporciona uns convenientes stores que actualizan os seus valores automáticamente cando o idioma seleccionado ou as traduccións cargadas actualízanse.",
   "introduction.list-items.features-4": "Unha variedade de funcions pra cargar paquetes de idiomas asíncronamente cando sexa necesario, utilidades para extraer o idioma predeterminado das cabeceras da petición HTTP en modo SSR",
   "introduction.list-items.features-5": "Tree-shaking completo de tódalas utilidades arriba mencionadas que a túa aplicación non precise",
-
   "icu-crash-course.title": "ICU syntax: Cursillo acelerado",
   "icu-crash-course.table-heads.definition": "Entrada",
   "icu-crash-course.table-heads.values": "Valores",
@@ -49,7 +47,7 @@
   "icu-crash-course.list-items.many": "(Tamén usado para fraccions)",
   "icu-crash-course.list-items.other": "(plural xenérico. O usado en idiomas con só unha forma de plural)",
   "icu-crash-course.table-cells.plurals-simple": "Your have {numCats, plural, one {one cat} other {# cats}}",
-  "icu-crash-course.table-cells.plurals-complex": "Your have {numCats, plural, =0 {no cats at all} one {one single cat} =2 {a couple cats} =3 {a trio of cats} =12 {a dozen cats} other {exactly # cats}}",  
+  "icu-crash-course.table-cells.plurals-complex": "Your have {numCats, plural, =0 {no cats at all} one {one single cat} =2 {a couple cats} =3 {a trio of cats} =12 {a dozen cats} other {exactly # cats}}",
   "icu-crash-course.table-cells.plurals-offset": "{guestCount, plural, offset:1 =0 {Mary does not give a party.} =1 {Mary invites {guest} to her party.} =2 {Mary invites {guest} and one other person to her party.} other {Mary invites {guest} and # other people to her party.}}",
   "icu-crash-course.subsection.select": "Select",
   "icu-crash-course.paragraph.select-1": "A utilidade <code class='inline'>select</code> úsase para elexir entre varias posibles traduccións en base ó valor dun argumento.<br> Inda que ten moitos usos o máis frecuente é para ter traduccións dependentes do xénero.",
@@ -70,7 +68,6 @@
   "icu-crash-course.subsection.number": "Números",
   "icu-crash-course.paragraph.number": "Formatea un número de acordo as regras do idioma seleccionado.",
   "icu-crash-course.table-cells.number": "Your account balance is {num, number}",
-
   "getting-started.title": "Primeiros pasos",
   "getting-started.subsection.installation": "Instalación",
   "getting-started.paragraph.installation-1": "Instala svelte-intl-precompile coma unha dependencia de runtime do teu proxecto Svelte.",
@@ -79,16 +76,21 @@
   "getting-started.paragraph.create-translations-2": "no raiz do proxecto, pero en realidade podes colocar o directorio onde prefiras",
   "getting-started.paragraph.create-translations-3": "Recomiendo usar ficheiros .json pero podes tamén crear ficheiros javascript que exporten un único obxeto que contén as traduccións. Calqueira que sexa a túa preferencia, as traduccións son simples cadeas coa sintaxis ICU:",
   "getting-started.paragraph.create-translations-4": "Eu prefiero o diccionario de traduccións teña un único nivel e usar puntos para crear xerarquías coma o de enriba, pero tamén podes aniñar obxetos coma a continuación:",
+  "getting-started.paragraph.create-translations-5": "¡JSON é demasido ríxido! ¡Quero máis flexibilidade!",
+  "getting-started.paragraph.create-translations-6": "Podes usar funcionalidades de JSON 5 nos teus ficheiros json. Por exemplo, podes usar comentarios, strings multi-línea, comillas simples, comas ó final de línas... <br>Funciona automáticamente.",
+  "getting-started.paragraph.create-translations-7": "Non me gustan as chaves",
+  "getting-started.paragraph.create-translations-8": "Como vexas. Si che gusta usar espacios puedes tamín utilizar ficheiros YAML. Tan so engade a extensión .yaml ou .yml. Se e que che van esas cousas.",
+  "getting-started.paragraph.create-translations-9": "Quero máis funcionalidades",
+  "getting-started.paragraph.create-translations-10": "Podes definir as túas traduccions en ficheiros .js, ficheiros .ts y ficheiros .mjs. O módulo debe exportar un objecto coas traduccións como o seu export por defecto.",
   "getting-started.subsection.hook-into-sveltekit": "Acomplar o compilador a SvelteKit",
   "getting-started.paragraph.hook-into-sveltekit-1": "O compilador desta librería necesita integrarse no proceso de complilado de SvelteKit do teu proxecto. Para elo engadep a lista de plugins de vite no teu <code class=\"bg-code px-2\">{path}</code>",
   "getting-started.paragraph.hook-into-sveltekit-2": "E xa está todo listo. Tempo de usar a librería.",
   "getting-started.subsection.hook-into-vite": "Acoplar o compilador a Vite.js",
   "getting-started.paragraph.hook-into-vite-1": "Se non estás a usar SvelteKit senon simplemente Vite.js a configuración é moy semellante. O fin e o cabo SvelteKit usa Vite.js internamente. Importa o compilador e engádeo á lista de plugins en <code class=\"bg-code px-2\">{path}</code>",
-
   "configuration.title": "Configuración",
   "configuration.subsection.example": "Exemplo de configuración",
   "configuration.link.example": "Exemplo",
-  "configuration.paragraph.example-1": "Este é o exemplo máis básico de inicialización da librería. Copia esto no teu",
+  "configuration.paragraph.example-1": "Este é o exemplo de traballo mínimo da inicialización da biblioteca. \nPon isto no teu",
   "configuration.paragraph.example-2": ".",
   "configuration.paragraph.example-3": "Esto es suficiente para ir comenzando pero vamos a profundizar máis en todas as opcions que tes.",
   "configuration.subsection.static-locales": "Engadir idiomas estáticamente",
@@ -119,13 +121,12 @@
   "configuration.definitions.navigator": "Extrae o idioma do navegador, que a súa vez é o idioma do sistema operativo.",
   "configuration.definitions.query": "Extrae o idioma no parámetro dado a query string da URL.<br>P.e <pre class='inline'>getLocaleFromQueryString('lang')</pre> para <pre class='inline'>/users?sort=name&amp;dir=asc&amp;lang=es</pre>",
   "configuration.definitions.hash": "Como <pre class='inline'>getLocaleFromQueryString</pre> pero para el hash de la URL.<br>P.e <pre class='inline'>getLocaleFromHash('lang')</pre> para <pre class='inline'>/users#sort=name&amp;dir=asc&amp;lang=es</pre>",
-  "configuration.definitions.path": "Extrae o idioma dos segmentos da URL.<br>P.e <pre class='inline'>getLocaleFromPathname(/^\/((es|en)(-\\w\\w)?)/)</pre> para <pre class='inline'>myapp.com/en-US/users</pre>",
+  "configuration.definitions.path": "Extrae o idioma dos segmentos da URL.<br>P.e <pre class='inline'>getLocaleFromPathname(/^/((es|en)(-\\w\\w)?)/)</pre> para <pre class='inline'>myapp.com/en-US/users</pre>",
   "configuration.definitions.host": "Extrae o idioma del host.<br>P.e <pre class='inline'>getLocaleFromHostname(/^((es|en)(-\\w\\w)?)\\./)</pre> para <pre class='inline'>https://pt.myapp.com</pre>",
   "configuration.subsection.custom-formats": "Formatos persoalizados",
   "configuration.paragraph.custom-formats-1": "Esta librería pode formatear números, datas e horas. Faino sen incrementar significativamente o tamaño do teu proxecto porque utiliza a API Intl xa presente en todos os navegadores modernos e main en Node.js.<br/>Por defecto a túa app dispón de estos formatos pero podes engadir os teus propios.",
   "configuration.paragraph.custom-formats-2": "Se queres definir os teus propios formatos pásaos ó incializar a librería usando a opción",
   "configuration.paragraph.custom-formats-3": ", os cuales serán engadidos ós formatos por defecto listados arriba. Os formatos deben ser obxetos válidos para pasar a",
-  
   "usage.title": "Uso",
   "usage.paragraph.preface-1": "A API de esta librería foi tomada en gran parte da excelente",
   "usage.paragraph.preface-2": ", hasta o punto de que na maioría de proxectos podes cambiar de svelte-i18 a svelte-intl-precompile e vice versa sen modificar a túa aplicación máis que actualizado o nome do paquete dende o que importas as funcions.",
@@ -147,4 +148,4 @@
   "usage.definitions.other-stores-1": "Pode ser usado para leer ou asignar o idioma actual. (P.e: <pre class='inline'>\"es-ES\"</pre>).",
   "usage.definitions.other-stores-2": "Contén a lista de idiomas rexistrados. (P.e: <pre class='inline'>[\"es-ES\", \"en\", \"pt-BR\"]</pre>).",
   "usage.definitions.other-stores-3": "Contén <pre class='inline'>true</pre> cando un idioma asíncrono todavía está cargando."
-}
+}