Localization

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
11 years ago
Hi,

I have not used nopcommerce for a long long time (last version I started to use as base for my shop was 1.3). I have downloaded 2.5 yeasterday and I wanted to do localization to Croatian.

What I want to ask is reason for having only 1 table for LocalStrings. Its really not so easy to maintain. Normaly I would have 2 tables (1 with resourcenames and second for translations). I try to think of reason for having it this way but can not find any :(.

Thank you!
0
11 years ago
Nobody?

I'm just curious why is localization done in the way it is. Everything else in nopCommerce is, if you ak me, is done in nice way.

I'm not saying localization is done wrong but I can not come up with good reason for not doing it with 2 tables (is easier to manage and its easy to derminate what string in waht language is not translated, ...)
0
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.