Localization alternative to Resx file
<p><strong>Why I don't want to use Resx files:</strong></p>

<p>I am looking for an alternative for resx files to offer multilanguage support for my project, due to the following reasons:</p>

<ul>
<li>I don't like to specify a "messageId" when writing messages, it is more effort and it is annoying for the flow as I don't see what the log message would actually say and I would need to open another tab to edit the message</li>
<li>Sometimes I use code inline because I don't want to create new variables for to easy steps (e. g. <code>Log.Info("Iterated {i+1} times");</code>). Using variables or doing simple calculations inline makes the whole code sometimes more clearly than creating additional code lines</li>
</ul>

<p><strong>What I could imagine instead:</strong></p>

<p>An external application which crawls a compiled exe for all strings, giving you the opportunity to ignore/add strings which should be translated. It could create a XML or Json file for all languages as well then. It would replace all strings with a hash/id so that a lookup for strings in all languages is still possible.</p>

<p><strong>Am I the only one who is not happy with the commonly used Resx / centralized string db solution? Do I miss points why this wouldn't be a good idea?</strong></p>