edit localization strings #1

devmondo commented 2013年04月01日 20:20:02 +02:00 (Migrated from github.com)

hi,
great work there,
if i have a customer who wants to have his own translation words, and i want to implement a UI to modify it, is there a way to that ?

and does this library use caching ?

thanks in advanced.

hi, great work there, if i have a customer who wants to have his own translation words, and i want to implement a UI to modify it, is there a way to that ? and does this library use caching ? thanks in advanced.

eric-b commented 2013年04月01日 22:46:31 +02:00 (Migrated from github.com)

Hi,

Each string is identified by itself plus its source (view path or class
name). So, the UI should enable edition of all strings within a given
source. The API does not provide a way to translate a specific word
(dictionary approach). There will be a lot of strings after a while, so
it ́s very flexible but this means you have a lot of translation work.
Update: UI will depend on your framework. For MVC, it represents some work but each application is very specific. For example, a synthetic data grid, or a form for each string (for long paragraphs). I thought of an UI bound to a translation API. Nevertheless, all of this cannot be implemented in a generic way. If you're looking for a ready to use localization API, try Griffin.MvcContrib. It ́s very similar to this API, and a UI is implemented. My goal was to implement a very generic and not invasive API with some extension points.

There is no cache for now. In my projects, I have a datalayer class (for
SQL Server) and a provider class which wrap the datalayer and implement
ILocalizedRepository. The cache (OutputCacheProvider) is implemented in the
wrapper. You can also implement directly ILocalizedRepository in your
datalayer. Anyway, cache should be managed by the implementation of
ILocalizedRepository.

Hi, Each string is identified by itself plus its source (view path or class name). So, the UI should enable edition of all strings within a given source. The API does not provide a way to translate a specific word (dictionary approach). There will be a lot of strings after a while, so it ́s very flexible but this means you have a lot of translation work. **Update**: UI will depend on your framework. For MVC, it represents some work but each application is very specific. For example, a synthetic data grid, or a form for each string (for long paragraphs). I thought of an UI bound to a translation API. Nevertheless, all of this cannot be implemented in a generic way. If you're looking for a ready to use localization API, try Griffin.MvcContrib. It ́s very similar to this API, and a UI is implemented. My goal was to implement a very generic and not invasive API with some extension points. There is no cache for now. In my projects, I have a datalayer class (for SQL Server) and a provider class which wrap the datalayer and implement ILocalizedRepository. The cache (OutputCacheProvider) is implemented in the wrapper. You can also implement directly ILocalizedRepository in your datalayer. Anyway, cache should be managed by the implementation of ILocalizedRepository.

devmondo commented 2013年04月02日 01:48:36 +02:00 (Migrated from github.com)

thank you very much for the detailed reply, it explains it will.

by the way i am a very big fan of you, and i always read your blog, and have learned a lot from your projects, and it gave me a very good start to create my own framework :)

all the best for you :)

thank you very much for the detailed reply, it explains it will. by the way i am a very big fan of you, and i always read your blog, and have learned a lot from your projects, and it gave me a very good start to create my own framework :) all the best for you :)

eric-b commented 2013年04月02日 22:41:20 +02:00 (Migrated from github.com)

It ́s nice to hear, thanks for this feedback.

It ́s nice to hear, thanks for this feedback.