I do recommend to use a software that supports unicode. Unfortunately VRD doesn't and won't be within any foreseeable future. Apparently they rely on many third party dlls not unicoded, so you can say they pretty much painted themself into a corner and can't get out without things getting really messy.The title editor displays only a few fonts in its listbox--far less than the many I have installed. I've put up with this for a good while, but now I'm working on a project that requires me to use other fonts. How can I make VDR recognize them?
I've done that before, but it's an unacceptably time-consuming interruption of workflow when it has to be done more than three or four times during a single project, which is the case right now....workaround: Create a graphic, with text, in another application such as paint, photoshop, etc. Then paste the graphic as the background in the title editor.
Although I agree that lack of Unicode support is a problem, it's not mine (at least right now); this particular system is dedicated to low-to-mid-level media work, so aside from VDR and the latest Irfanview, most of the software is what some folks would consider out of date. The fonts are from CorelDraw 9 suite (ca. 2001), which did not feature unicode fonts AFAIK. The ANSI limitation shouldn't be an issue with most of these older fonts either, but Dan's note about that did prompt me to investigate another possibility, which turned out to answer the question: the reason my fonts aren't being displayed is because VideoReDo won't accept Type 1 fonts. With these older fonts I prefer to use Type One fonts over True Type because True-type fonts are less stable (especially when you're trying to get fancy with desktop-publishing projects). So I've got all my nice designer fonts installed as T1, and that's what the title editor doesn't like. I just deleted two of them and re-installed them as True-types, and the title editor font box now displays those fonts.software that supports unicode. Unfortunately VRD doesn't
Well, as I indicated, I wouldn't expect you to. The real issue is that the limitation isn't documented, so I had to waste a bunch of time figuring it out. Kinda makes one feel that RTFMing is pointless.there is no way for us to add support for Type 1 even if we wanted to.Dan