<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >True Story, Christian - thanks for the pointer.<div><br></div><div>Can I ask you to open an issue on github.com about separation of localization? </div><div><br></div><div>We need to address this proper</div><div><br></div><div>Thanks</div><div><br></div><div>Tom</div><br><br><br>-------- Ursprüngliche Nachricht --------<br>Von: Christian Reiner <foss@christian-reiner.info> <br>Datum: <br>An: owncloud@kde.org <br>Betreff: Re: [Owncloud] howto exclude translation,
order of entries in localisation menu <br> <br><br>Hello Stefan, hello all, <br><br>On Thursday 05 September 2013 09:17:19 Stefan Vollmar wrote:<br>> it is desirable (for many reasons) to have localisations of user interfaces<br>> for as many languages as possible. However, OwnCloud ships with two German<br>> versions, one of them quite informal. As our installation is for "official"<br>> purposes only, the more formal version is the right choice. We already had<br>> a case where somebody (unintentionally) selected the informal setting, then<br>> shared a file by link - this could be potentially awkward: you do not see<br>> the mail template which is sent to the recipient (and it is not suitable<br>> for our purposes).<br><br>actually in my eyes this shows up a more general problem. Your approach to <br>solve your issue at hand by disabling a certain localization is the wrong one <br>and steps short in my eyes: <br><br>The templates chosen for outgoing messages should not depend on the session <br>language chosen by the user at all! Those are two completely separate things!<br>Imagine a foreign member of your company, say a russian speaking colleague. He <br>intuitively would use the russian localization of owncloud if available. And <br>this certainly totally makes sense, since this is what localizations are there <br>for. But most likely you do not want outgoing messages to your customers to be <br>in russian language, just because the user initiating the message uses a <br>russian localization! <br>It is a very typical pattern in software suites that localizations of the user <br>session and of persistent content being generated must be independent. This is <br>currently not the case, apparently. <br>So in my eyes the correct solution to your problem would be to decouple these <br>localization use cases instead of disabling a random localization set. <br><br>Christian Reiner (arkascha)<br>_______________________________________________<br>Owncloud mailing list<br>Owncloud@kde.org<br>https://mail.kde.org/mailman/listinfo/owncloud<br></body>