MMXII Posted January 26, 2015 Posted January 26, 2015 First I'd like to mention that the way how translating works in IPS4 is handled very nicely. For example, I love the singular/plural options as well as the quick editing in the frontend. Auto-saving while translating is a great thing to have and also running multi-language sites was never easier.That being said, I still see a lot of room for improvements:Please always allow complete translations of IPS4. Currently, unless you own all addons for IPS4, the translations are not complete. Phrases of addons that you don't own do not show up in the language file. I'd love to see complete language files where you can translate all phrases, no matter if they are actually used by the current installation.Please allow separate frontend/backend translations. I don't know why everything was put into one language file, maybe to make things easier or simplier, maybe phrases are being used in both the frontend and backend at the same time. Anyways, not everyone needs or wants to have a translated AdminCP, very often a frontend-only translation will be more than enough. So please allow us to split up the language file between a frontend and a backend part.Personally I also liked the way it was done in v3: one language pack for every addon. However if one was always able to fully translate IPS4 (the first thing I mentioned above), then I'd also be fine with the current situation.
TheSonic Posted January 26, 2015 Posted January 26, 2015 Please allow separate frontend/backend translations. I don't know why everything was put into one language file, maybe to make things easier or simplier, maybe phrases are being used in both the frontend and backend at the same time. Anyways, not everyone needs or wants to have a translated AdminCP, very often a frontend-only translation will be more than enough. So please allow us to split up the language file between a frontend and a backend part.+1. And add the Option to choose the ACP language . or (my favorite) just add a languageselector in the footer like in the frontend
Andrej Posted January 26, 2015 Posted January 26, 2015 +1. And add the Option to choose the ACP language . or (my favorite) just add a languageselector in the footer like in the frontend You can already do that.
TheSonic Posted January 26, 2015 Posted January 26, 2015 Whoops, i really missed that one...Great, thank you @Andrej
alexch Posted January 25, 2016 Posted January 25, 2016 Please allow separate frontend/backend translations. I don't know why everything was put into one language file, maybe to make things easier or simplier, maybe phrases are being used in both the frontend and backend at the same time. Anyways, not everyone needs or wants to have a translated AdminCP, very often a frontend-only translation will be more than enough. So please allow us to split up the language file between a frontend and a backend part. This is something they should consider seriously. Right now, I want to reniew my license and upgrade to IPS 4.1 but I can't until they improve that. I need to translate the forum, but I don't want to translate the whole product, just the frontend.
TheSonic Posted January 25, 2016 Posted January 25, 2016 See the Topic in the pre-sales (oh, it's awaiting aproval right now)... If you only want to trnslate the Forums, Translation Tools -> QuckTranslating may be your friend
Recommended Posts
Archived
This topic is now archived and is closed to further replies.