Reply to thread

Message

<blockquote data-quote="davidf" data-source="post: 710088" data-attributes="member: 19484">I don't think that it as simple as a Localization folder as you'd need to multiple plugins there i.e. one strings_de contains 90% of what you want so you need another.&nbsp; It actually makes a lot of sense to push the language files to where they should be (in the plugin which the tanslation is for) but again there are a number of issues with that approach - what do you do if one of the plugins is not present when the language pack is installed.I have a few assumptions based on the fact that english strings should be present for each plugin - which may be nonsensical to some plugins, but something consistent is needed to build everything else on.Producing a full plugin would not really be an issue but one of the things I don't like is that dependencies could not be done properly i.e. a plugin with the German language for online videos could not depend on online videos as if there is a translation for my tv series present then that would not be loaded if online videos was not present (that's why pushing the translations to the plugins seems nice).The best way I can come up with at the minute is to put an attribute in the section which says which plugin is refered too - and this defaults to the current plugin where the attribute is not specified.&nbsp; That seems to give the flexibilty needed while still making languages identifiable to their plugin.&nbsp; It also allows identification of missing/extra translation strings easy <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; I had been using English as the base for that idea but it could have went very wrong.</blockquote>

[QUOTE="davidf, post: 710088, member: 19484"] I don't think that it as simple as a Localization folder as you'd need to multiple plugins there i.e. one strings_de contains 90% of what you want so you need another. It actually makes a lot of sense to push the language files to where they should be (in the plugin which the tanslation is for) but again there are a number of issues with that approach - what do you do if one of the plugins is not present when the language pack is installed. I have a few assumptions based on the fact that english strings should be present for each plugin - which may be nonsensical to some plugins, but something consistent is needed to build everything else on. Producing a full plugin would not really be an issue but one of the things I don't like is that dependencies could not be done properly i.e. a plugin with the German language for online videos could not depend on online videos as if there is a translation for my tv series present then that would not be loaded if online videos was not present (that's why pushing the translations to the plugins seems nice). The best way I can come up with at the minute is to put an attribute in the section which says which plugin is refered too - and this defaults to the current plugin where the attribute is not specified. That seems to give the flexibilty needed while still making languages identifiable to their plugin. It also allows identification of missing/extra translation strings easy :) I had been using English as the base for that idea but it could have went very wrong. [/QUOTE]

Verification