I would second the addition of a Latin locale. I have been running into a few issues in the past couple years as I develop some applications in PHP that have strings in a number of languages, among which is Latin. However since there is no Latin locale in the system, none of the strings in Latin can be handled through `gettext` or any kind of localization functions in PHP (such as the soon to be deprecated `strftime`, or the newer `IntlDateFormatter`, just to mention a couple examples). Which means I can handle all translatable strings through `gettext` with the exception of Latin, which I have to hardcode into my applications. This makes for an application that becomes hard to maintain, it would be so much easier to just be able to handle any Latin translations just like any other language that is supported by the application.
I would second the addition of a Latin locale. I have been running into a few issues in the past couple years as I develop some applications in PHP that have strings in a number of languages, among which is Latin. However since there is no Latin locale in the system, none of the strings in Latin can be handled through `gettext` or any kind of localization functions in PHP (such as the soon to be deprecated `strftime`, or the newer `IntlDateFormat ter`, just to mention a couple examples). Which means I can handle all translatable strings through `gettext` with the exception of Latin, which I have to hardcode into my applications. This makes for an application that becomes hard to maintain, it would be so much easier to just be able to handle any Latin translations just like any other language that is supported by the application.