Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1205368" data-attributes="member: 82144">What do you want me to say?Fine, so you don't consider it an improvement. Not everything is going to be to your liking. That's life. I can only repeat what I said in my earlier reply: either customise your installation (which in this case will require recompiling - again, that's life), or propose a change.If you're going to propose a change, please be constructive. By &quot;constructive&quot; I mean: please don't just say that you think the change should be optional and stop there. This doesn't really help anybody, and some people will even consider it to be moaning/complaining (=&gt; ignore). Go further. Start a thread and/or polls to find out what other people actually think. Propose how the change could be made optional. If via a setting:<ul>
<li data-xf-list-type="ul">What should the setting be called?</li>
<li data-xf-list-type="ul">Where should the setting be?</li>
<li data-xf-list-type="ul">What should the default value be?</li>
</ul>etc.Make your case.I'm happy to take your word that there were indeed numerous references. However &quot;numerous references&quot; is not the same as &quot;99,9%&quot; that catavolt mentioned. Also, who's to say that those references were actually representative of the majority?I don't have any strong personal feelings about whether the &quot;now&quot;/&quot;next&quot; text should or should not be displayed in the mini-guide. I'm simply arguing that the translation files should contain accurate translations. That's it.Why?It's easy to understand if you consider an example.An English-speaking developer who is unaware of this &quot;exception&quot; in the translation files develops some new window.This developer decides they need to have &quot;now&quot; or &quot;next&quot; in the window.Obviously it makes sense to reuse existing strings where possible, so they check the English string files.They find the existing strings and think it's fine to use them.When German users come to use the new window:<ul>
<li data-xf-list-type="ul">the layout may be messed up 
</li>
<li data-xf-list-type="ul">the window usage/meaning may be incomprehensible</li>
<li data-xf-list-type="ul">etc.</li>
</ul>This is why I'm so opposed to what has been done.Can you not understand where I'm coming from?Again, I'm not opposed to the removal of the &quot;now&quot;/&quot;next&quot; text from the dialog. I just don't like how it has been done.</blockquote>

[QUOTE="mm1352000, post: 1205368, member: 82144"] What do you want me to say? Fine, so you don't consider it an improvement. Not everything is going to be to your liking. That's life. I can only repeat what I said in my earlier reply: either customise your installation (which in this case will require recompiling - again, that's life), or propose a change. If you're going to propose a change, please be constructive. By "constructive" I mean: please don't just say that you think the change should be optional and stop there. This doesn't really help anybody, and some people will even consider it to be moaning/complaining (=> ignore). Go further. Start a thread and/or polls to find out what other people actually think. Propose how the change could be made optional. If via a setting: [LIST] [*]What should the setting be called? [*]Where should the setting be? [*]What should the default value be? [/LIST] etc. Make your case. I'm happy to take your word that there were indeed numerous references. However "numerous references" is not the same as "99,9%" that catavolt mentioned. Also, who's to say that those references were actually representative of the majority? I don't have any strong personal feelings about whether the "now"/"next" text should or should not be displayed in the mini-guide. I'm simply arguing that the translation files should contain accurate translations. That's it. Why? It's easy to understand if you consider an example. An English-speaking developer who is unaware of this "exception" in the translation files develops some new window. This developer decides they need to have "now" or "next" in the window. Obviously it makes sense to reuse existing strings where possible, so they check the English string files. They find the existing strings and think it's fine to use them. When German users come to use the new window: [LIST] [*]the layout may be messed up [*]the window usage/meaning may be incomprehensible [*]etc. [/LIST] This is why I'm so opposed to what has been done. Can you not understand where I'm coming from? Again, I'm not opposed to the removal of the "now"/"next" text from the dialog. I just don't like how it has been done. [/QUOTE]

Verification