File Away Needs Your Feedback on Translations
-
Hi, File Away Users. Thom here.
I’m working on the next big release. I’ve rewritten the entire plugin in object-oriented PHP, improved some features, fixed about a hundred little bugs, but now I’m working on making the plugin translation ready. The way I see it, there are three options:
1) Make only the front-end, public face of File Away translatable (i.e., any text you see on the front-end page, including messages from operations, etc.).
2) Make everything except for the tutorials translatable. This includes Settings Page tabs, labels, options, and the modal options. Just none of the help info or tutorials.
3) Make absolutely everything translatable, including all the tutorials.I am leaning toward option #1, not because I don’t want the extra work of setting up the tutorials for translation (currently I’ve set it up for option #2, but I’m considering undoing all the back-end stuff I’ve done and paring it down to option #1). If we’re just doing translations of the front-end stuff, it will be a lot less daunting for translators; we’ll be able to churn out new translations faster, and won’t have to worry as much about updating translations whenever I tweak a tutorial or option, etc.
What do you think?
- The topic ‘File Away Needs Your Feedback on Translations’ is closed to new replies.