Profiler uses the Tahoma trutype fonts. Try reinstalling.

Quoting Taro:

Quote:
Quoting 8ballMax:

Quote:
Profiler uses the Tahoma trutype fonts. Try reinstalling.

Reinstall DVD Profiler? Thanks, I'll give that a try.

I think 8ballMax means re-install the Tahoma TT Font; that has helped a number of people who've had issues with blank buttons etc.

As to losing unused retailers... on the repair database options you have the chance to do Full Basic or custom. you notice on Custom you can choose to Remove Unused Cast, Crew, Studios etc... this is automatic in Full Repair so I sugest you use Custom and untick these options.

FWIW I do suspect you're right that some of the problems are caused by not being in unicode...

Thanks, I'll try reinstalling the Tahoma TT font ... in fact, I think this font is by definition not installed in Japanese Windows, so I'll have a look into that (perhaps install from the Windows install DVD?)

As for removing the unused retailers, that was indeed my fault for not unticking that options. Sorry, false alarm there 

However, I use the external repair database utility every time, yet each time I make even the tiniest modification in a movie where accented words are used, that messes up my database and I get that 'duplicate key' error. I keep going back and forward between the program itself and the database repair utility ...

unicode not being supported is most likely the cause. Any idea if this will be supported in future updates? For asian OS users, this is really a 'must have' ... not only would this solve many of the database errors, it wil alsol allow us to use asian text in our local database modificiations. For example, when I buy a Japanese Blu-ray, I want to input it in Japanese instead of using a transcription in roman letters.

Quoting lmoelleb:

Quote:
Yes, this is due to lack of Unicode support. You can change the ANSI codepage to 1252 (under regional settings somewhere, might be named something with "non-unicode applications"). But then obviously the system will start messing up Japanese ANSI text.

Or install a virtual machine with English settings and run it there.

There is a reason no one has used ANSI code pages for anything serious for the last decade.

Thanks for your reply. So my fear is justified and the lack of unicode support is severly messing up my database. Setting ANSI to 1252 would indeed solve the problem but mess up plenty of other software, so that's not a feasable option.

A virtual machine is a good idea. Do you have any link to a short explanation on how to do this?

I have multiboot (Win XP in Japanese as well as the US version) on my main computer, but having to reboot every time I want to use DVD Profiler isn't really practical. If launching a virtual machine is quicker, then I might just do that until an update of DVD Profiler fixes this issue (hopefully)

Quoting Giga Wizard:

Quote:
maybe this can help:
http://itknowledgeexchange.techtarget.com/itanswers/windows-xp-virtual-machines/

thanks, I might give that a try. I just hope my computer's processor and memory will be able to handle running 2 Windows XP's at once.

But if it works, it's a decent make-do solution until DVD Profiler internal solution can be found.

First of all, mad thanks to all of you who have tried to help me.

I tried the virtual machine sollution but it seems my computer(s) have trouble running two XP's at once.

So instead, I'll try multiboot with one XP being the US version. Normally, that should solve the problem for the time being but it's far from ideal. I really hope for a more definitive solution from Invelos as I can't keep rebooting every time I want to go into DVD Profiler ....

Quoting xradman:

Quote:
Have you tried MS applocale?  You can start DVDProfiler with applocale locale set to the US (while still in Japanese OS) and see if that will work for you. 

MS Applocale

Awesome suggestion! Even better than dual booting or running a virtual machine, if it works! I'll give it a try this evening. Lots of thanks for the support and help!

If that fails, I'll just manually edit out accented (unsupported) characters and lock those fields so they don't get updated ... that should also work but I prefer your applocale solution 

Thanks a lot!