We Put Half a Million Files in One Git Repository, Here’s What We Learned

Re:We Put Half a Million Files in One Git Repository, Here’s... by haizzz on Thursday June 16, 2022 @02:36AM (#31763067)

hey hey author here, xlf files are translations that are coupled with the texts we set in the code so they're not really generated I admit that was misleading. What I wanted to get across is they're not touched directly by engineers but they're still created through our translation pipeline where real humans translate them

[ Parent | on HN ]

Re:We Put Half a Million Files in One Git Repository, Here’s... by necovek on Thursday June 16, 2022 @06:08AM (#31764270)

How do you split your XLIFF files? Does each project get one big one and the proliferation is simply due to number of languages, or do you have a more granular split (eg. if you've got one component, it will have dozens of XLIFF files for every language, instead of one per language)?

By the numbers you mention, 70% of the files make a ratio of code files to translation files 1-3, so unless you only support 3-5 languages, it's definitely not one XLIFF file per source file, so I wonder at what granularity it is?

(My experience is mostly with localizations using GNU gettext tools, and you usually do a small-finite-number of PO files per project per language, where that small-finite number is exactly one for like 99% of projects)

[ Parent | on HN ]

Re:We Put Half a Million Files in One Git Repository, Here’s... by auscompgeek on Thursday June 16, 2022 @08:09AM (#31765074)

It's one XLIFF file per locale per component, not including the source en_US. We currently support 104 locales.

More info: https://news.ycombinator.com/item?id=28931601

[ Parent | on HN ]

Re:We Put Half a Million Files in One Git Repository, Here’s... by necovek on Thursday June 16, 2022 @02:31PM (#31769375)

Thanks: that's still a lot of components (3000+) if you've got at least 300k xlf files!

Good job managing all that regardless of the approach :)

[ Parent | on HN ]