These three files are probably the best places for you to start.  :) 

Though, you'll probably find additional shared values in the <code>GlobalResources</code> and <code>SharedResources</code> files as well. 

Awesome! Thanks Will.

I found most of the labels for login under "Global Resources -> SharedResources" in case somebody need this. Regards.

Yeah, most of them.  That's why I was a bit vague.  Depending on the use case(s) you need to support, I'm pretty sure that there will be a bit of overlap across localization files.  

As there is no "better" tool in DNN, I always use the "Find in files" function of Notepad++ for that, setting the folder to the DNN root, include sub-dirs and filter to "*.resx". I always found what I was looking for...

Happy DNNing!
Michael

Awesome recommendation Michael! Thanks

To Michael's point, I also find it easier to first use a third-party (and external) tool to find things in the localization files.  They're just too many and many of the key/value pairs don't make sense where they are.  You can waste a lot of time in the DNN UI trying to find things to translate if you don't already know where to look for them.  

Personally, Mark Saunders introduced me to FileLocator Pro (and Lite) years ago.  That's where my screenshot came from. Both versions are equally powerful for all of the daily tasks I've ever had to perform.  I mainly use Notepad++ for notes I don't care about losing, for viewing log files, quick code edits, etc.  

What's to follow is not an ad and I don't get anything for saying any of this.  I just LOVE this tool.  It's saved me many hours of time over the years for all kinds of tasks.  Maybe Notepad++ can do all of this too.  I'm just far more familiar with the features in the one I use.  

By the way, if any of you begin using FileLocator Pro/Lite, the following file exclusion list is something I use all of the time. I use this when I'm searching through source code.  It works faster and more thoroughly than Visual Studio ever can - especially through larger or multiple project folders at the same time.  This exclusion list prevents the search from looking into files that you don't care about.  This is a tool that I often use to deep dive into source code and other files to find deeply-rooted hacks.  

<code>NOT:*.cache;*.FileListAbsolute.txt;*.dll;*.pdb;*.jmx;*.ide;*.ide-wal;*.designer.cs;*.zip;*\node_modules\*.*;*.suo;*.bak;</code>

Here is what that might look like in practice.  Imagine if the exclusion wasn't there...  You'd have to look through all kinds of VS, .NET, backup, and DLL files.  

The only reason I've found to get Pro (vs Lite) so far is that you can exclude (or include) child folders in several cool ways with Pro.  So, the folder value <code>C:\Work\Dnn.Modules\</code> could be updated to include something like <code>;-.git</code> to omit searching for any subfolder that matches that name.  

So, this somewhat useful search... 

Now, using the additional parameters (<code>C:\Work\Dnn.Modules\;-.git;-Build</code>) can look like this:

HUGE difference!  😎 

Will, thanks for your recommendation! 

Will, thank you for reminding me of that long-lost program for me. I couldn't remember the name of it to save my life! LOL. It is a GREAT program!