OK TheLastCayen, while you can post a bug report as WP suggested, I reckon you will get a lot further if you track the actual problem down and, ideally provide a fix.
While I normally work on Linux, I make install packages for Windows and the translation appears to work fine, I ship only .mo files of course.
So, back in your Lazarus IDE, open {lazarus source}/lcl/lcltranslate.pas, you can get there from the entry in your 'uses' line.
Go to about line 95, function FindLocaleFileName(LCExt: string; Lang: string; Dir: string): string;
Thats the function that attempts to find po and mo files. Incidently, apart from wasting a few cycles, its all you need to decide to use non-english or not, you don't need to check in your own code for the presence of the files.
Set a break point at the fist 'begin' and set a watch on 'Result' and you can step through the functions attempts to open your translate files. Last time I did this I notes that it tried to open -
/home/dbannon/Pascal/tomboy-ng/tomboy-ng/es/tomboy-ng.mo
/home/dbannon/Pascal/tomboy-ng/tomboy-ng/languages/es/tomboy-ng.mo
/home/dbannon/Pascal/tomboy-ng/tomboy-ng/locale/es/tomboy-ng.mo
/home/dbannon/Pascal/tomboy-ng/tomboy-ng/locale/es/LC_MESSAGES/tomboy-ng.mo
/usr/share/locale/es/LC_MESSAGES/tomboy-ng.mo
My app, pretty obviously, is tomboy-ng and in this case its launched from /home/dbannon/Pascal/tomboy-ng/tomboy-ng/, I don't see any mention of it trying in a directory one up from current directory but maybe I found what I was trying to understand and stopped watching.
Also as I noted above, you need two .mo files, one with the same name as your executable (less the .exe in your case) and one that has the LCL constants, when you generate it, its called lclstrconsts.mo and lives in the same place as {your-app}.mo
If you are seeing some things translated and some not, it could be that you have only one of the required files, or it could mean that your .po file is not being updated as you add extra string constants. Lazarus automatically puts the string constants you use in the ObjectInspector but you need to declare other string constants as "RESOURCESTRINGS".
But, anyway, I strongly advise you to really track down the bug before logging a report, you will get far better attention if you do.
Davo