#i18 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #i18, aggregated by home.social.
-
Changes in French purchases of pulses during an FAO awareness campaign https://www.diningandcooking.com/2549567/changes-in-french-purchases-of-pulses-during-an-fao-awareness-campaign/ #AwarenessCampaign #BoxCoxDoubleHurdleModel #francais #france #French #FrenchDiet #I18 #NutritionalGuidelines #Pseudopanel #PulsesPurchases #Q18 #SustainabilityJELCodes:D12
-
So what's the smoothest way these days to integrate localisation repositories into your git repo?
As a background: our localisation needs to live in a separate git repo that is monitored and also updated with new translations by pootle (a translation tool) but we also want to be able to pull out the generated PO files as well as push local updates (and new texts) from within the containing project repo the localisations belong to. So merges / rebates are kinda required.
Git submodules are the worst case here as you can't really commit / push local updates to the translations back to the localisation repo without making a separate checkout, doing your changes there, then pushing to your remote and finally updating the reference for your local submodule and pulling again.
Git subtrees sounded like a good idea but they way they're implemented makes them nasty to use as well.. they tend to break if you work with pull --rebase in the containing repo and merge conflicts in the sub tree can't be resolved with a sub tree-rebase either.
In the past I used to have the localisation as a full git checkout in a sub directory of the containing project and maintained it using a few CMake scripts but I had hoped there's be something smoother by now.
#git #submodules #subtree #localisation #i18 #workflows #question #SofwareDevelopment #boostswelcome
-
Elevate Your Translations with AI Translation Customization | Toglee Blog
https://tolgee.io/blog/releasing-ai-customizations -
Upcoming Changes to Tolgee's Pricing Plans | Toglee Blog
https://tolgee.io/blog/new-pricing-2024-01 -
Say hi to Autonomous Localization (i18n) of your app | Toglee Blog
https://tolgee.io/blog/autonomous-localization -
How to setup Tolgee with Next.js App Router | Toglee Blog
https://tolgee.io/blog/how-to-setup-tolgee-with-nextjs-app-router -
Stay Local While Going Global: Product Localization Playbook | Toglee Blog
https://tolgee.io/blog/product-localization -
Importing data to Tolgee using custom JS and Axios | Toglee Blog
https://tolgee.io/blog/importing-data-to-tolgee-using-axios -
Tolgee Unreal Plugin – Seamless Game Localization | Toglee Blog
https://tolgee.io/blog/unreal-plugin -
How to Localize Your Vue Application with Tolgee? | Toglee Blog
https://tolgee.io/blog/how-to-localize-vue-app -
The Key to Translation: The Ultimate Guide to Naming Translation Keys | Toglee Blog
https://tolgee.io/blog/naming-translation-keys -
Case Study: How Fluent Search Boosted Productivity in a Multilingual World | Toglee Blog
https://tolgee.io/blog/case-study-fluent-search -
Tolgee Figma Plugin – Streamline Your Localization Process | Toglee Blog
https://tolgee.io/blog/figma-plugin -
Web site rant / Je râle du web
I am tired of websites that are available in various languages BUT only rely on browser settings. I can't pick French, because my browser is in English. Why ? (Hint: there's no good reason for this)
J'en ai marre des sites web qui sont disponibles en plusieurs langues mais qui ne se basent QUE sur les préférences du navigateur. Je ne peux pas choisir anglais, car mon navigateur est en français. Pourquoi ? (Indice : Il n'y a aucune bonne raison)