[Mesa-dev] [PATCH mesa] xmlpool: update translation po files
Eric Engestrom
eric.engestrom at intel.com
Tue Nov 13 17:07:02 UTC 2018
On Tuesday, 2018-11-13 13:37:14 +0000, Emil Velikov wrote:
> On Mon, 12 Nov 2018 at 18:14, Dylan Baker <dylan at pnwbakers.com> wrote:
> >
> > Quoting Eric Engestrom (2018-11-12 09:47:22)
> > > On Monday, 2018-11-12 16:56:32 +0000, Emil Velikov wrote:
> > > > On Mon, 12 Nov 2018 at 14:24, Eric Engestrom <eric.engestrom at intel.com> wrote:
> > > > >
> > > > > These files are close to 4 years out of date; a lot's changed since.
> > > > > Let's just check in a recently-regenerated version.
> > > > >
> > > > Worth removing them from git and letting the build regenerate them as needed?
> > >
> > > No, the point is for them to be filled with the translations.
> > > They aren't 100% generated, they're more like "refreshed" by running the
> > > ninja command, to add new strings to be translated and adjust file/line
> > > references.
> > >
> > >
> > > That said, I've just looked at the state of the translations, and
> > > "partial" is already generous. Users would currently get a mostly
> > > english driconf interface with a few strings translated here and there,
> > > which I'm not sure is worth the hassle of maintaining all this.
> > >
> > > Should we just drop the translation infrastructure?
> >
> > I'd try pinging the people who provided the translations in the first place to
> > see if they're interested in updating them. If not I'd be in favor of dropping
> > unmaintained translations, if there are no maintained translations drop the
> > whole things.
> >
> > Just my 2ยข
> >
> Very well said Dylan. I'm on the same page.
Sounds like a good plan; I'll ping them privately and we'll see from there :)
More information about the mesa-dev
mailing list