Hey folks,
In development of DarkEDIF, I'm establishing that all the extensions manually open a INI file and read a list of languages. I'd prefer if a functionality for multi-language support was added into MMF2 instead.
More information can be found Please login to see this link., under the top feature.
This would be useful for optimisation and would mean rather than forcing a combo box property in all the extensions containing all the available languages, which if changed will not affect any other DarkEDIF extensions, MMF2 would be able to select a list of languages for the actions/conditions/expressions to be written in.
Request for change for the SDK
Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
-
-
No response... was this refused, not read, on the todo list?
-
You mean MMF2 doesn't already tell extensions what language it is using? I though that was how the inbuilt extensions changed language with MMF2...
-
It only has 3 languages, English, French, and Japanese. And those are set by the resource file, so you have to compile 3 times more MFXs.
-
MMF2 only has those three languages. What's the point in translating your extension to a different language than the editor?
-
because this is SortaCore? >:)
-
Well, this change will ensure you only need one MFX for support of those three languages and a bit further.
-
I think this can only be a good idea myself, surely the more languages supported the bigger the possible user base for MMF2...
-
To clarify on my response, even if the extensions only had those three languages, this would centralise all the three languages to one MFX file as opposed to requiring recompilation for each language into a different MFX. This change will in turn allow extension updaters to work more efficiently with multilingual extensions (as the MFXs have to be built and distributed with different MFX names).
-
Edif already supports alternate JSON files for different languages. How would this improve on that?
-
That would be the content of my last post...
If you don't see this request as having merit, you can delete this thread.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
