+1

Will localization of documentation be involved or is this solely about software localization?

Localization of documentation as well software localization will be not involved in this.

This is more from i18n side

• Making sure flatpack will provide fluent support for all language components. including fonts, input method, locales.

• Modularity for i18n packages. IBus, IBus input method, fonts etc.

• Glibc and Unicode common locale data repository sync. (Already some work has been started in upstream)

So more on technology side of localization and languages.

In last flock we discussed good to have FAD dedicated on localization side somewhere in Europe. Albania/Hungary/Brno or France, we will further discuss on it this flock and may be plan in FY18 Q2.

This doesn't necessarily make a big difference in the decision but just for my own knowledge, can you explain what the practical advantages of "Glibc and Unicode common locale data repository sync" will be? It sounds good but I don't know what it means. :)

Good question.

• Unicode CLDR has been adopted by all major OS provides. Including Mac, MS, IBM, Google etc.
• Unicode CLDR is many locales which are not available in Glibc and more verified data from community. They are growing with excellent speed.
• Its huge advantage for Glibc, to have it sync with Unicode CLDR.
• Same time, Glibc is minimal locales and CLDR is dedicated with many fields, so we only need to sync subset of CLDR with Glibc localedata.
• This is our (i18n) next step after improving Glibc Unicode update method.

After flock couple more people shown interest for i18n FAD, looking forward to update budget and members information soon.

Revised proposal:
After flock, we have one more attendee. Revised budget request: $4725, since flight ticket cost may vary while booking.

Requesting budget approval for $5000.

We are planning to execute this around November. Will be very helpful, if we can work on this ticket quickly.

Ping..

I am now +1 to this. I'd like to see us vote on this in today's meeting if possible, if not via the ticket ASAP. I suggest we approve a budget of $6800 as requested with an authorization for me to allow it to overspend by $1200 in case airfare has gone crazypants :). @pravins I can work with you on getting the airfare purchased.

@mattdm - please include this ticket today.

@jkurik was +1 in the meeting, and I am too, and we have no -1s, so this is approved.

Thanks for the approval.
@bex yeah, getting airfare purchase will be very useful. Will ping you with exact information.