Problem is that the file open dialog return name of the file in unicode (with any non-ascii characters that may be there), while the core expect const char* (8bit ) when opening the file. Probably the name got converted in a bad way (as ascii and not in the local codepage)
I personally usually tend to avoid non-ascii filenames, because of similar problems in most applications, so I have not noticed this bug :) However, the fix should be relatively simple - add proper conversion to appropriate places. I added the conversion and I was able to open files with accented characters in it, so this should be fixed now. The fix is now in CVS, so release 0.3.1 will be fixed once it will come out. You can test the CVS version in meantime. Martin Petricek On 4/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > > as with 0.2.5. I still can't open certain files. xpdf doesn't have any > problem to open them. on trace level 5 I get the following output. I am using > the normal open dialog to open that document, hence I can't see what I made > wrong. It looks like that the problem is the filename, as soon as the > filename has a german umlaut, e.g. öüä, the problem occurs. Is anyone reading > this able to open a file with a name using a non latin 1 character? > > I am running suse 10.0 where everything should be unicode. > > Regards, > K. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Pdfedit-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pdfedit-support
