topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Monday August 3, 2020, 4:38 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Bug with filenames (accented characters)  (Read 148 times)

elbitjusticiero

  • Supporting Member
  • Joined in 2020
  • **
  • default avatar
  • Posts: 1
    • View Profile
    • Donate to Member
Bug with filenames (accented characters)
« on: July 02, 2020, 06:11 AM »
Hi everyone! First of all, mouser, thanks for this wonderful piece of software. I had used a couple of launchbars and even programmed my own before finding this one which is near-perfect. It now lives permanently at the top of my screen.

I wanted to point out a bug (or lack of a feature) when using folder nodes. In this case, filenames with accented letters (á, Ó, etc.) are interpreted wrongly: the characters come out as a´, O´, etc. This is not a cosmetic issue: clicking on the files brings up an error because it can't be found under that name.

Interestingly, folder names don't have this problem: I can have a path like, say, E:\Revistas\Nueva Dimensión\ND19.epub and the file will open fine. The issue only comes up with the file names.

It also happens for some files and not for others. I can't pinpoint a fundamental difference, but it's there.

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 40,323
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: Bug with filenames (accented characters)
« Reply #1 on: July 02, 2020, 01:35 PM »
That's interesting regarding folders working.. I was going to say that LBC just doesn't support unicode paths, but if its working for folders that's strange.  It may be a difference between how windows itself translates certain characters.  There's probably a way to refer to the file paths enocded in a way that LBC can reach them..