avatar image

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

Login with username, password and session length
  • October 21, 2018, 03:58 AM
  • Proudly celebrating 13 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

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - losiek [ switch to compact view ]

Pages: [1]
FARR Plugins and Aliases / Re: Locate32 Plugin for FARR by Okke
« on: December 30, 2007, 02:19 PM »
No, I don't think that yours bugs are caused directly by lack of Unicode support, but I think that they're related. It seems that your bug work very similar to my ' (accent) bug. Can you check Location column in "loc +" results? Are there two (or more) paths for one file?

OK, so everybody is waiting now for your Unicode plug-in. Let's hope it will resolve other bugs also :) Good luck.

FARR Plugins and Aliases / Re: Locate32 Plugin for FARR by Okke
« on: December 29, 2007, 08:15 PM »
OK, so everything I know at the moment:
1. Console in Windows XP can produce full Unicode output but only for displaying. Piping and redirecting is unsupported so it's useless for us.
2. Standard printing functions like wprintf (used in locate.exe) uses built-in WideCharToMultibyte conversion (to DOS codepage in my case), so polish letters have wrong hexcodes in normal windows.
3. I'm able to write raw Unicode to console (swprintf+WriteFile, without widechar->codepage conversion) - when displaying it look like there are spaces between all letters, but after redirecting to a file it works like a charm (even without BOM :) ).

So everything we need now is widechar implementation of Locate plug-in. I don't have Delphi so I can't play with that :( Anybody have seen Okke recently? Maybe you have enough time to make plug-in with integrated Locate :)

I think it's unresolvable at the moment. We have to wait for fixes or full Unicode version of this plug-in.

FARR Plugins and Aliases / Re: Locate32 Plugin for FARR by Okke
« on: December 29, 2007, 04:07 PM »
I'm having trouble building it though, but I guess building your foundation-class-thingy library and adding it to %INCLUDE and %LIBS will fix that :)
If you still have problems with compling this - download source from this page: It has necessary 3rd party libs and headers needed for compilation.
I played a little with writing results to a file and I finally forced locate to write in full Unicode:) But I'm rather inexperienced programmer and I used some dirty tricks to achieve that.
Maybe someone in the future will write a plug-in that gets results directly from Locate database;) On the other hand - we *just* have to wait until FARR will have built-in indexing. That will make this plug-in unnecessary... to beautiful to be real. ;)

I'm soo lame :/ (or maybe Windows is?) In order to write wide characters correctly file need to be opened in binary mode. Then fwprintf works perfectly. No dirty hacks are needed.

FARR Plugins and Aliases / Re: Locate32 Plugin for FARR by Okke
« on: December 28, 2007, 07:15 PM »
Unfortunately I'm not  sure how does this stupid console work :(
I think you are right about redirection detection. Look at That's exactly the same thing you said:) I used that example in my testapp.

Can you redirect your output to a file (if it'll work at all) and then open it using notepad? In my case displaying using WriteConsoleW and WriteFile works fine but redirection works only with WriteFile (WriteConsoleW gives 0-byte file). But when I open created file with notepad I still get messed Unicode characters :(

I think that Locate should provide option to directly write results to a file (without console and redirection) or simple library interface for searching.

FARR Plugins and Aliases / Re: Locate32 Plugin for FARR by Okke
« on: December 28, 2007, 05:40 PM »
Thanks for tips:)

Locate uses Unicode (at least to write console) if databases use Unicode  (you can check this in the settings dialog of locate32.exe).
There is other thing. Locate uses Unicode, but Windows console doesn't. In Windows XP console uses old DOS-style 8-bit codepages to display diacritic characters. In my case (polish language) console uses CP852 codepage and standard windows uses Windows-1250 codepage (or full Unicode). So searching works fine but polish letters are displayed incorrectly in FARR (they have different hex codes in those 2 codepages - thanks to M$) and real Unicode characters (Hebrew, Arabic, Greek etc.) don't work at all. :(

FARR Plugins and Aliases / Re: Locate32 Plugin for FARR by Okke
« on: December 20, 2007, 02:49 PM »
(sorry for my english :( )
I found a weird bug in locate32 plug-in. It's related to ' (apostrophe) key procsessing in result list. I found same results with ` (accent) key, so maybe other keys are also affected.
When in search results are filepaths that include ` or ' then next links are messed up:
I see only 3 results (there should be 24). When I use locate.exe manually everything is working fine, every line is correct with CR/LF at end.
I have little sugestion. Could you place execution of locate.exe in seperate thread? Because when I'm typing or changing text to search, and results are updated there is a little freeze for a secod or a half. This is only a minor issue, but it would be nice if you can fix that.

I also have a question - is it possible to make loc results scoreable? That's the only thing that prevents me from making Locate plug-in my primary search engine in FARR (will it ever have an indexed search - it's so slooow now. I've reading some old posts about making it in near future, but I don't see indexing on official feature list... will be it ever made?).

Thanks in adavance

Pages: [1]