As per here, the language setting isn't preserved currently with ToDoList 6.5.x
I've identified the issue, and will have a fixed build sent for uploading this evening.
New: Kanri (Oct 9, '24), Platform 29.5.3 (Jun 27, '24)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
I've hit a snag on this, and need some input from NSIS gurus. Here's my launcher.ini.
As you can see, I'm doing a FileWrite for language switching which includes a value that has environment variables in it, but I'm unable to have environment variables in the corresponding LanguageFile section when using ConfigRead.
In order to have the language processed correctly, I need to have the path cut off, hence the configRead vs. using an INI read.
So, what I'm looking for is a way to custom-code a configRead or entry that allows for environment variables.
Any thoughts? I'm willing to replace the relevant section of Languages.nsh with a custom hook, just need to know how.
[EDIT] I think adding a ${ParseLocations} section would suffice, from looking at other spots that use environment variables, but I'm unsure (at least at this hour) where to locate it.
Entry=LanguageFile=$PAL:AppDir%\ToDoList\Resources\Translations\
->
Entry=LanguageFile=%PAL:AppDir%\ToDoList\Resources\Translations\
I'm not sure if this is the problem. If not, we could use TrimLeft… oh wait.
Previously known as kAlug.
I had tried both ways, and was changing it back. Missed that one. I think I've figured out what's needed. If it works, I'll submit a patch for PAL.
I've fixed the issue, and sent an update to John for posting.
Technical details:
I disabled the Language Init Hook, and reimplemented it in Custom.nsh as a Pre Hook, including ParseLocations for the ConfigRead and INI Entry sections. This isn't ideal, and as such, I've submitted a patch for PAL to have this available by default.
Hello
I have the same problem in version 6.6.7
Hope it is easy to solve it.
Thank you
Bye
Please start a new post, starting the title with [BUG], that states exactly what the problem is, your full install path, os version, app version, the language you're having a problem with, as well as how you're launching - ie, from the platform or stand-alone.