Character problem and Videostudio 11+

Moderator: Ken Berry

micononos

Post by micononos »

Svuppe wrote:I have an interesting observation (with regards to the character problem in VS, not this forum).


Now for the news: If I select a US english keyboard layout, I am suddenly able to use ALT 0229 etc and get my danish characters. Weird huh?
Hi Svuppe
It's the same thing for me and i understood the reason why VS was working on my computer with XP ... It have an US keyboard !.. and i am using a soft to access the french latins characters à é è etc .
On the other computer i use Vista with a french keyboard so it does'nt work..
->Little mistake of ours Ulead Americans friends ? :
-To write french with french version of VS you must use an US keyboard and to get "strange accents " use " ALT something " :shock:
Thanks for all you have done Svuppe , now with your help i know a little better how are working fonts .
Best regards
dani75
Posts: 7
Joined: Sat Aug 04, 2007 12:58 pm
Location: PARIS - FRANCE

Post by dani75 »

Hello everybody
I have bothe versions 10+ and 11+, and a french keyboard.
Now I am able to tell you that the problem with accented characters (like the one we have for french) is only with VideoStudio 11. With VideoStudio10, they appeared correctly. So, to my opinion, it is a regression, just appeared in VideoStudio11 when Ulead added the enhanced functionalities for subtitles.
Here is the proof:
Image
Image
Moreover, using the ALT key with codes provides correct characters with the french keybord displays correct characters in Winword, but incorrect characters in VideoStudio11 (for example: ALT 0232)..
I informed the Ulead technical support yesterday, I got a reply that they were working on it, but were unable to see the bug for the moment.
However, thank you to Svuppe, who did a remarquable workaround for this bug. It works perfectly.

Dani75
Svuppe
Posts: 82
Joined: Sun Dec 25, 2005 11:51 pm
Location: Denmark
Contact:

Post by Svuppe »

I am very happy to hear that they are working on this problem. My little "fix" isn't the right way to go. In essence I've destroyed part of a font (central europe) for those of us that don't need that subset. It works for me, and some of you as well, but many other nationalities still have problems, as they are in need of another subset of the font.

My guess is that a country-lookup goes wrong somewhere in VideoStudio. US english users gets classified (correctly) as to use the "western" character subset, and everything works fine for them. This also explains why a lot of users never see this problem. If one use a US english keyboard, ALT nnnn works perfectly for our accented letters.
Danish, swedish, norwegian, french (and others) wrongly gets classified as to use the "central europe" character subset. We should belong to the "western" subset instead.
But this is only my humble guess.
dani75
Posts: 7
Joined: Sat Aug 04, 2007 12:58 pm
Location: PARIS - FRANCE

Post by dani75 »

Hello everybody!

I have just found a third nice workaround of the problem with special characters. We are neither more obliged to use Svuppe's special font, nor to switch back to VideoStudio 10.

Remember: the bug appeard when Ulead added the new subtitle functionalities, and among them is the compatibility with the Unicode coding. We will use this new functionality. Refer to http://unicode.org/charts/.

Therefore, in order to display correctly special characters with Video Studio 11, follow this procedure:

1) Enter your titles ; they will display badly, as you know. No matter!
2) Use the option "record the subtitle file" (sorry if the name of the option is not correct, I have translated it from french). This produced a file with extension ".utf".
3) Actually, the format of subtitles inside is compliant to the SRT encoding. Therefore, use a MS window to change the extension to ".srt"
4) Use a software to convert your file using Unicode coding. Personnaly I used the "SubResync" software of the "VobSub" package. You can find this at http://www.pc-infopratique.com/telechar ... obsub.html. Once SubResync executes, you chose "open", you select your "srt" file, then click on "Save As", YOU TICK THE "Unicode Output" BOX, and you enter a new name for your file.
5) You just have to go back to Video Studio 11, and select the option "open the subtitle file" with any font. There is no need to change the extension of your file to ".utf".
6) Your display looks now correct !!!

Hope this will be helpfull to everybody.

Dani75
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Gigabyte B550M DS3H AC
processor: AMD Ryzen 9 5900X
ram: 32 GB DDR4
Video Card: AMD RX 6600 XT
Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
Location: Levin, New Zealand

Post by Ken Berry »

Does that work only with 'true' sub-titles i.e. ones which can be turned on or off on the final DVD? Or does it also work with fixed titles e.g. a Title and rolling credits, which are a permanent display in your video?
Ken Berry
dani75
Posts: 7
Joined: Sat Aug 04, 2007 12:58 pm
Location: PARIS - FRANCE

Post by dani75 »

Yes, it works for any application of the "title" step.

However, I am a bit embarrassed, because I just realize that, with this method, the letters having problems (only a subset of the letters with accents) appeared actually without their accent, like in english, ... like you can do it with your keyboard as well !

Therefore, this is not really a workaround of the bug, for it has allowed to highlight... another bug: Video Studio 11 does not handle the unicode character set properly !

Therefore, as Svuppe wrote, we can only hope that Ulead will hear the user's complaint and correct these bugs.

dany75
micononos

Post by micononos »

Hi All
As already said by svuppe . I think the best way to work around the bug if you want to use another font than the Svuppe's font is to declare two types of keyboard in the computer configuration .

- Your keyboard layout ( French or danish or portuguese etc )
- US keyboard layout

-Now you can write all the texts you need with your country keyboard declared and the font you want.
-Then you have only to switch to US keyboard in configuration and substitute the wrongs letters using ALT ****

You only need ascii table of the characters you use ( ****), ( easy to find on the net ).

It works fine with my french keyboard disguised in a genuine yankee keyboard ....

it' also possible to convert the font you want as Svuppe did but its is a piece of work ..

It's true that Core/Ulead must solve this bug.
knud
Posts: 1
Joined: Wed Sep 12, 2007 10:50 pm

Post by knud »

This is a workaround.

How to get special (danish) characters:
Use a Font Editor, I use FontCreator, "Open a font", copy/past individual characters, rename the Font Family Name: "Tools", "Autonaming", Like "ArialNew", "Font", "Install".

Ulead Unicode

Copy ae past to 0107
Copy oe past to 0159
Copy aa past to 013A

Copy AE past to 0106
Copy OE past to 0158
Copy AA past to 0139

"ae" is the of course the real danish letter, cant display them here.
luis_c274

Post by luis_c274 »

Hello:
I have the same problem that you, but with the letters ñ or Ñ.
The only solution is to modify the font using a font editor??
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Gigabyte B550M DS3H AC
processor: AMD Ryzen 9 5900X
ram: 32 GB DDR4
Video Card: AMD RX 6600 XT
Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
Location: Levin, New Zealand

Post by Ken Berry »

Or, has been suggested in earlier posts in this thread, change your keyboard temporarily to the US keyboard layout, and then use the standard ANSI international codes for your characters... Ñ, ñ, à, æ, é etc
Ken Berry
luis_c274

Post by luis_c274 »

Ken Berry wrote:Or, has been suggested in earlier posts in this thread, change your keyboard temporarily to the US keyboard layout, and then use the standard ANSI international codes for your characters... Ñ, ñ, à, æ, é etc
Thanks.-
It works Well. -
It costs to me to read in ingles, but it attempt.-
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Gigabyte B550M DS3H AC
processor: AMD Ryzen 9 5900X
ram: 32 GB DDR4
Video Card: AMD RX 6600 XT
Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
Location: Levin, New Zealand

Post by Ken Berry »

De nada ... y muy buena suerte!
Ken Berry
dani75
Posts: 7
Joined: Sat Aug 04, 2007 12:58 pm
Location: PARIS - FRANCE

The end of the workarround for the accented chars ?

Post by dani75 »

Good news!

The bug is dead, God saves the bug !

Corel has discreetly put in line 3 update packs for Ulead Video Studio 11 / 11 Plus. This is what they call "version V11.5". See the following link:
http://www.ulead.com/tech/vs/vs_ftp.htm

I tried them, and can you guess how I have been surprised?
Not only the french accented characters can now be typed and are displayed correctly, but also this software release seems to be much much more stable than the V11 Plus! Before trying it, it was quite frequent that, while editing a video clip, the software suddenly crashed.

I found important to tell you about this.

So long...
Dani75 :D
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Gigabyte B550M DS3H AC
processor: AMD Ryzen 9 5900X
ram: 32 GB DDR4
Video Card: AMD RX 6600 XT
Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
Location: Levin, New Zealand

Post by Ken Berry »

Um... thanks. But we've know about those updates, beginning 6 November, when the first patch was released. The Power Pack was released a few days later. And the third -- the Hot Fix -- should only be used if you had experienced the specific problem outlined in the note below it (installation of the SDK).

But I am glad they corrected your problem, as they already have for lots of other users! :lol: :lol: :lol:
Ken Berry
Post Reply