Open stevehalliwell opened 4 years ago
@stevehalliwell Quick question; would it be possible that, since the aforementioned Unity localisation package is not ready for production anytime soon, to extend the Localization.cs script instead, to have an extra option to pull all text from canvases and such from the scene, just like it pulls strings from flowcharts in the scene, and export it into a separate csv? I thought this is what the "Export Standard Text" button did at first, when I saw it (I know it doesnt).
So when you click the "export non-Fungus text" button lets say, it pulls all the non-Fungus text from the scene and offers you to export it into a csv file.
To add to my previous post; I'd like to better understand your original post/proposition; would this task involve to find a solution to support localising the non-Fungus text in games with the new official Localization package, or are you proposing to make all of Fungus be compatible with the Localization package instead of the localisation features it's currently using?
Is your feature request related to a problem? Please describe. Unity has packages in preview that will provide a standard way to deal with localization of strings and assets, link. It also discusses a standard way of localizing the text of editor tools, link
Describe the solution you'd like Once these are stable, it warrants investigation to determine if Fungus' existing Localization can be switched to be backed by Unity's package, or if the Fungus, localization can be removed entirely.
On the Editor side, we presently don't offer any localization and we should. We would have to rely on community or funding to do the translation work itself though.