MODX Staff
This was my original idea (fallback to file after looking in database), but the fact that you can import from/export to file at any time is plenty of flexibility in my mind. I’d much prefer not to complicate the loading of these from database and or file. We are at the point that we need to reduce core overhead (i.e. optimize), not increase it. We can think about this more for 2.1 possibly, but the import/export is plenty of flexibility IMO.
Yes, that’s what I was envisioning, although I’m not sure it’s actually possible unless language tags can also specify the language (or manager_language is used -- but that has its own problems). I guess whether MODx searched for the corresponding file automatically and whether it logged that event could be two system settings.
I do not agree here, the only lexicons that belong under the core are the core lexicons. Lexicons that go with extensions or add-ons can go wherever that add-on or extension defines, and that is generally within the core/components/<component-name>/lexicon/ directory. In fact the component root location should be defined by the namespace in my opinion, and configurable at installation; there will be more obvious reasons for this need as we move forward with various multi-site configurations.
Whether we do that or not, I’d like to see a standard place for language files. I don’t think it’s an unreasonable imposition on the developer since it shouldn’t create any significant performance penalty and it would allow a lot of options down the road that aren’t possible with language files in unpredictable places.
That sounds reasonable to me.
Quote from: BobRay at Aug 27, 2009, 02:34 AMThis was my original idea (fallback to file after looking in database), but the fact that you can import from/export to file at any time is plenty of flexibility in my mind. I’d much prefer not to complicate the loading of these from database and or file. We are at the point that we need to reduce core overhead (i.e. optimize), not increase it. We can think about this more for 2.1 possibly, but the import/export is plenty of flexibility IMO.
Yes, that’s what I was envisioning, although I’m not sure it’s actually possible unless language tags can also specify the language (or manager_language is used -- but that has its own problems). I guess whether MODx searched for the corresponding file automatically and whether it logged that event could be two system settings.
Quote from: BobRay at Aug 27, 2009, 02:34 AMI do not agree here, the only lexicons that belong under the core are the core lexicons. Lexicons that go with extensions or add-ons can go wherever that add-on or extension defines, and that is generally within the core/components/<component-name>/lexicon/ directory. In fact the component root location should be defined by the namespace in my opinion, and configurable at installation; there will be more obvious reasons for this need as we move forward with various multi-site configurations.
Whether we do that or not, I’d like to see a standard place for language files. I don’t think it’s an unreasonable imposition on the developer since it shouldn’t create any significant performance penalty and it would allow a lot of options down the road that aren’t possible with language files in unpredictable places.