TB54 Salut TB54 et merci pour les encouragements et la remontée. Néanmoins, nous avons traduit tout ce qui était possible de notre côté, il s'agit donc d'une clé de langue qui est directement incluse dans le code source. Dès que j'aurai un peu de temps, j'irai soumettre ce problème aux développeurs de Flarum.

Encore merci ! 💪

    Malheureusement ce texte n'est pas dans Flarum mais il est codé en dur dans le template du bbcode dans la librairie de formattage qu'on utilise https://github.com/s9e/TextFormatter/blob/2.11.0/src/Plugins/BBCodes/Configurator/repository.xml#L299

    Il faudrait d'abord que ce texte soit rendu traduisible dans cette librairie, et ensuite qu'on le source à partir du traducteur Flarum. Un autre problème c'est que dans certaines langues le mot devra aller avant le nom d'utilisateur et il n'y a actuellement aucun système en place pour gérer ça dans un template de formattage. Et ajouter un mot unique dans un fichier de traduction est "bad practice" dans ce cas puisque ce ne sera pas suffisant pour certaines langues.

    20 days later

    C'est encore (plus) du détail, mais est-ce que le pack de language peut facilement inclure de la typographie ?

    Je pense par exemple à l'insert automatique d'espaces incompressibles avant les ! ? ; : (pour éviter qu'un de ces signes se retrouve seul à la ligne).

    Ou encore d'automatiquement transformer les - en – quand il est suivi d'un mot (comme sous word), pour pouvoir utiliser des tirets larges de rupture en cours de phrase (façon point virgule).

      TB54 normalement oui, n'importe quel caractère Unicode peut être intégré dans une traduction. Il faut peut-être utiliser un format spécial pour l'intégrer dans le fichier Yaml. Je pense que les projets gérés dans Weblate convertissent automatiquement ces caractères dans Yaml si nécessaire.

      En ce qui concerne le contenu généré par les utilisateurs (posts, bio, etc) à nouveau tous les caractères Unicode devraient être supportés. Pour faire des conversions automatiques il faudra par contre ajouter soit du code PHP (server side), soit du code javascript (client side). Je crois que la librairie TextFormatter fait déjà certains remplacements automatiques via la syntaxe Markdown. Flarum n'a pas de système spécial en place pour faciliter ça. Un pack de langue pourrait le faire, mais aussi n'importe quelle extension dédiée.

        10 days later

        Hello everyone! We just released version 3.7.0 of the French language pack. This version is compatible with the Flarum 1.3.0 release and translates several new third party extensions. Have a nice update!

        Bonjour tout le monde ! Nous venons de publier la version 3.7.0 de la traduction française. Cette version est compatible avec la nouvelle version de Flarum 1.3.0 récemment disponible et traduit plusieurs extensions tierces supplémentaires. Bonne mise à jour !

        12 days later

        Hello ! Un autre mini-truc corrigeable à l'occasion, quand on change les étiquettes d'un topic et qu'une annonce s'affiche entre deux messages :

        Plutôt "a ajouté l'étiquette".

          a month later

          TB54 Ce sera normalement corrigé lors de la prochaine version, en espérant que cela ne créé pas une autre erreur ailleurs. Merci !👌

              10 days later

              Hello everyone! We just released version 3.9.0 of the French language pack. This version is compatible with the Flarum 1.4.0 release and translates several new third party extensions. Have a nice update!

              Bonjour tout le monde ! Nous venons de publier la version 3.9.0 de la traduction française. Cette version est compatible avec la nouvelle version de Flarum 1.4.0 récemment disponible et traduit plusieurs extensions tierces supplémentaires. Bonne mise à jour !

              18 days later

              I'm not sure where this would be best discussed, but I noticed this language pack includes translations for my premium Formulaire extension.

              The extension already ships with its own French translation which I maintain on every update, so there's no need for this language pack to handle it.

              I'm definitely not against providing alternate translations, but in this case it might actually create more confusion because I noticed a lot of the wording is different from my own translation, so when I add new strings there are inconsistencies between this language pack which is used by default and the new texts which use my own text.

              Currently I don't have a French documentation page, but if I ever add one then it will be a mess because many settings don't have the same name in the bundled translation and this language pack.

              In particular: "Formulaire indépendant" vs "Formulaire autonome", "Réponses" vs "Soumissions", "Tags" vs "Étiquettes".

              And there are a few sentences that have become nonsensical, but I don't expect anyone to be able to translate them without seeing them in context. I don't really want to go chasing incorrect translations in the pack when I bundle a verified translation with the extension already.

              I didn't find a way to override this pack's translations from my extension, and since people are expected to install this pack to enable the French language, there doesn't seem to be a way for people to use my official translation anymore without creating a custom stripped-down French language pack 😬

              I would suggest dropping all translations in the kilowhat-formulaire namespace from this pack if that's possible.

              I could exclude French translations for this extension on Weblate. I already have list of exceptions for extensions that have bundled translations, but it is hard to track this for all extension, and basically impossible for premium extensions. @Qiaeru Any objections?

                There is also a simple solution: @clarkwinkelmann , you can contribute on the French language pack by submitting tour contributions for your extension on Weblate. I will accept all your contributions, so you can avoid including a translation in your extension.

                If tout don't want to, @rob006 we can effectively exclude this extension from the language pack.

                However, I think it is too bad to not to take advantage of the language pack, which standardizes all terms used in Flarum, official extensions and third-party extensions, which is better for the users.

                But I respect the will of the extension author (and it will be less work for me!), so I'm waiting for his reply. 😊

                  Qiaeru I would agree for open-source extensions, but since this is a closed source extension most translators will likely not have access to, I see more downsides managing translations publicly versus doing it manually. If I'm going to review every new translation anyway, it's much simpler for me to do it at the same time as the English text while working on the extension locally.

                  My 2 main concerns are incorrect translations due to lack of context, and the inability to control the release. I run this extension in production for myself and clients in French and there are times where I need an update to be shipped quickly including new French translations. Admittedly this hasn't happened in a while, but it's an ability I want to continue guaranteeing.

                  With the current set of tools I have a hard time believing a complex private extension with hundreds of translation strings can be reliably community-translated. There needs to be additional hints and comments in the source code made available for translators, and while I'm sure this could be achieved with Weblate I don't think we have anything close to this yet? If there's a way to add this to the extension source code I would definitely consider it and maybe it would allow to move French to the same level as other languages I don't speak.

                  As for the standardization of terms, luckily most terms are unique to the extension so there's no conflict with Flarum itself. Only exception is tags. I don't really like its French translation, hence why it's not used in my extension 🙉

                  rob006 I could exclude French translations for this extension on Weblate

                  I think that would be best for the time being.

                  I remember we discussed this for other of my extensions in the past. I thought we had talked about this one already, but that wasn't the case.

                        clarkwinkelmann No problem, I understand your arguments and if it's possible to exclude the extension from our language pack (poke @rob006, I don't see any issue. 👍

                        While we're on this, @clarkwinkelmann, do you have any other extensions you want to exclude from the language pack?

                            Qiaeru there are a few others, but it doesn't matter as much since those aren't paid extensions. I have one more paid extension in the work that will be released with French, but it's still in a while, I'll ping you.

                            I don't have a definite list but for the open-source ones there's clarkwinkelmann/flarum-ext-passwordless, clarkwinkelmann/flarum-ext-email-as-display-name, clarkwinkelmann/flarum-ext-see-past-first-post, clarkwinkelmann/flarum-ext-silent-mailchimp (abandoned)

                            I'm generally not against community translation for my "low support" open-source extensions because if someone else wants to maintain it, it will give me an excuse to drop it from the package the next time someone sponsors a new feature if they don't want to pay for the translations to be updated in a language they won't use. On my "actively supported" open-source extensions I will generally continue updating the French texts because usually it means I'm running the extension on my own websites.

                            Generally for new work I suggest my client contribute the translation to the language pack themselves, and only ship English. It's been a long time since I've included non-English languages in a new open-source extension.

                              a month later

                              Version v4.0.0

                              General changes:

                              • Removed outdated Flarum core translations (version 1.3 or higher is supported).

                              Added support for new extensions:

                              Updated and/or removed outdated translations for extensions:

                              Removed support for outdated extensions:

                              All changes: v3.9.0...v4.0.0.

                              In order to update run these commands:

                              composer require flarum-lang/french
php flarum cache:clear

                              This version removes support for older versions of Flarum and some outdated extensions. Before updating make sure you're using the most recent versions of Flarum and extensions.

                              It would be nice to have a few more languages ​​added, so it would be fun as many languages ​​as possible, the better

                              14 days later

                              Version v4.1.0

                              Modifications générales:

                              • Mise à jour des traductions du noyau de Flarum.

                              Prise en charge de nouvelles extensions:

                              Mise à jour des traductions de certaines extensions:

                              Journal de toutes les modifications : v4.0.0...v4.1.0.

                              Veuillez exécuter les commandes suivantes pour lancer la mise à jour :

                              composer update flarum-lang/french
php flarum cache:clear
                              2 months later

                              Version v4.2.0

                              Modifications générales:

                              • Mise à jour des traductions du noyau de Flarum.

                              Prise en charge de nouvelles extensions:

                              Mise à jour des traductions de certaines extensions:

                              Journal de toutes les modifications : v4.1.0...v4.2.0.

                              Veuillez exécuter les commandes suivantes pour lancer la mise à jour :

                              composer update flarum-lang/french
php flarum cache:clear

                              Version v4.3.0

                              Prise en charge de nouvelles extensions:

                              Mise à jour des traductions de certaines extensions:

                              Journal de toutes les modifications : v4.2.0...v4.3.0.

                              Veuillez exécuter les commandes suivantes pour lancer la mise à jour :

                              composer update flarum-lang/french
php flarum cache:clear