The FTP protocol supports translation of response texts (while FTP commands and codes never change).
Support for text translations was implemented through ILocalizationFeature and the NGettext dependency and its ICatalog and Catalog types.
The NGettext catalog attempts to load translation files - but by default fails as there are no translation files.
This changeset drops the NGettext dependency in favor of implementing our own interface. The interface surface is reduced by defining only the methods we use (GetString).
This is a breaking change. The impact is likely very low. Few people will have used or implemented custom translations. For those that did, a fixup is simple.
Users who previously implemented and registered an ICatalog for custom text translation will have to instead implement ILocalizationCatalog. This is a trivial type reference replacement - the two methods we use are equal on both interfaces.
Users who made use of NGettext library magic translation file loading (I assume it may identify and load files if placed correctly) will need to implement a simple forwarding catalog type.
References:
Fixes #144
RFC 2640 Internationalization of the File Transfer Protocol
ite-klass
commented
8 months ago
The FTP protocol supports translation of response texts (while FTP commands and codes never change).
Support for text translations was implemented through
ILocalizationFeatureand the NGettext dependency and itsICatalogandCatalogtypes. The NGettext catalog attempts to load translation files - but by default fails as there are no translation files.This changeset drops the NGettext dependency in favor of implementing our own interface. The interface surface is reduced by defining only the methods we use (
GetString).This is a breaking change. The impact is likely very low. Few people will have used or implemented custom translations. For those that did, a fixup is simple.
References: