GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 

GenoPro Support Forum




Part of the letter is replaced by a question mark.

Click to view RSS...
Author I can not type some characters via the keyboard of the Sakha (Yakut) language.
Posted Tuesday, February 28, 2012 - Post #29866
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1

Last Login: Yesterday @ 11:52 AM
Posts: 4,886, Visits: 22,781
fbukolyi (28-Feb-2012)
Dan when you wrote 'The problem is the Yakut language does not have any code page,', what does it mean? According to m$ there are two codepages for Yakutsk, 0085 and 0485 (  http://www.microsoft.com/resources/msdn/goglobal/default.mspx?OS=Windows%207 ), both refer to ANSI 1251 and OEM 866.

Thanks for the link.  This is very useful page.  I already had entered 1251 as the Code Page in the Language tab (Menu -> Tools -> Display Alphabets -> Language).

I made an update version, as my function CodePageFromLangID() returns was returning a zero value for the Yarkut language.  I am crossing my fingers this will work, because I suspect the WM_CHAR sent by Windows has already been translated.

Posted Tuesday, February 28, 2012 - Post #29869
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Friday, October 24, 2014
Posts: 37, Visits: 309



http://support.genopro.com/Uploads/Images/28a97dd4-ef3a-4b52-abc7-f98c.jpg

Кэскилгит кэҥээтин!
Хоһоонор, кэпсээннэр: Бикитиэкэ
Сахалыы энциклопедия: Бикипиэдьийэ
Posted Tuesday, February 28, 2012 - Post #29870
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Friday, October 24, 2014
Posts: 37, Visits: 309
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=33 (0x00000021), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=33 (0x00000021), lParam=131073 (0x00020001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=237 (0x000000ED), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=237 (0x000000ED), lParam=33751041 (0x02030001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=252 (0x000000FC), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=252 (0x000000FC), lParam=196609 (0x00030001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=228 (0x000000E4), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=228 (0x000000E4), lParam=33816577 (0x02040001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=252 (0x000000FC), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=252 (0x000000FC), lParam=262145 (0x00040001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=63 (0x0000003F), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=327681 (0x00050001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=63 (0x0000003F), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=393217 (0x00060001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=63 (0x0000003F), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=458753 (0x00070001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=63 (0x0000003F), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=524289 (0x00080001)
GetKeyboardLayout() returned 0x04850485
ConvertWmCharToWmUniChar() - uChar=63 (0x0000003F), cpKeyboardCodePage=1251
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=589825 (0x00090001)
WndProcEditW() - WM_CHAR: wParam=237 (0x000000ED), lParam=33751041 (0x02030001)
WndProcEditW() - WM_CHAR: wParam=252 (0x000000FC), lParam=196609 (0x00030001)
WndProcEditW() - WM_CHAR: wParam=228 (0x000000E4), lParam=33816577 (0x02040001)
WndProcEditW() - WM_CHAR: wParam=252 (0x000000FC), lParam=262145 (0x00040001)
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=327681 (0x00050001)
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=393217 (0x00060001)
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=458753 (0x00070001)
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=524289 (0x00080001)
WndProcEditW() - WM_CHAR: wParam=63 (0x0000003F), lParam=589825 (0x00090001)


Кэскилгит кэҥээтин!
Хоһоонор, кэпсээннэр: Бикитиэкэ
Сахалыы энциклопедия: Бикипиэдьийэ
Posted Tuesday, February 28, 2012 - Post #29871
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Friday, October 24, 2014
Posts: 37, Visits: 309
I quote the words of Michael Kyraһa (not a member of the forum):

How to reproduce the bug (Steps to reproduce):
1. In Windows Vista or 7 add a keyboard layout using the standard Control Panel. The language name is "Yakut (Russia)".
2. Start GenoPro
3. Focus into a text field (Person's First Name for example)
4. Switch your keyboard to Yakut and type "1234567890" using the top row on the keyboard (don't use numpad and don't use clipboard).
5. Check what you have just produced.
  5.1 If the string reads: "!ньдьҥҕөһү;:-=" - then the program works correctly.
  5.2 If the string reads: "!ньдь?????;:-=" - that's incorrect and you've reproduced the bug.
PS: Although code page 1251 is called Cyrillic. it never supported full Sakha (Yakut) alphabet. Microsoft assigned it by mistake (They promised to fix it in 8th version of Windows). But anyway, the only way to encode Sakha(Yakut) symbols is UTF-8, UTF-16 or other Unicode (multibyte) encodings.

Кэскилгит кэҥээтин!
Хоһоонор, кэпсээннэр: Бикитиэкэ
Сахалыы энциклопедия: Бикипиэдьийэ


Edited: Tuesday, February 28, 2012 by Halan
Posted Wednesday, February 29, 2012 - Post #29877
Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Important Contributors
Customers
GenoPro version: 3.1.0.1

Last Login: Saturday, December 28, 2024
Posts: 193, Visits: 4,270
In case if you have some time to read : http://www.ifapcom.ru/files/Documents/multiling_eng.pdf

on page 251 it is said: 

Fonts
The fonts are to contain the characters of the Cyrillic code table of the Unicode
standard, version no earlier than 5.1, with Russian letter glyphs and the following
glyphs of the officially recognised Yakut letters and letters of the smaller peoples of
the North residing in the Republic of Sakha (Yakutia):
Һ – CYRILLIC CAPITAL LETTER SHHA (code 04BA)
һ – CYRILLIC SMALL LETTER SHHA (code 04BB....

Maybe it is worth to try this as well: http://42.ykt.ru/stuffs/fonts.htm


Feri
Posted Wednesday, February 29, 2012 - Post #29878
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1

Last Login: Yesterday @ 11:52 AM
Posts: 4,886, Visits: 22,781
Unfortunately, I believe the bug is deeper than this.  Until GenoPro is recompiled as a native Unicode application, Windows will keep sending the question mark (?) character as WM_CHAR.  I have the feeling that all the non-Unicode applications have the same problem for the Yarkut language.
Posted Wednesday, February 29, 2012 - Post #29879
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Friday, October 24, 2014
Posts: 37, Visits: 309
GenoProSupport (29-Feb-2012)
Unfortunately, I believe the bug is deeper than this.  Until GenoPro is recompiled as a native Unicode application, Windows will keep sending the question mark (?) character as WM_CHAR.  I have the feeling that all the non-Unicode applications have the same problem for the Yarkut language.
Maybe refer to the Microsoft developers?


Кэскилгит кэҥээтин!
Хоһоонор, кэпсээннэр: Бикитиэкэ
Сахалыы энциклопедия: Бикипиэдьийэ
Posted Thursday, April 12, 2012 - Post #30018
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Friday, October 24, 2014
Posts: 37, Visits: 309
Is there something new?

Кэскилгит кэҥээтин!
Хоһоонор, кэпсээннэр: Бикитиэкэ
Сахалыы энциклопедия: Бикипиэдьийэ
Posted Thursday, May 10, 2012 - Post #30123
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Customers
GenoPro version: 2.5.4.1

Last Login: Friday, October 24, 2014
Posts: 37, Visits: 309
Still I'm waiting for good news)))

Кэскилгит кэҥээтин!
Хоһоонор, кэпсээннэр: Бикитиэкэ
Сахалыы энциклопедия: Бикипиэдьийэ
Posted Monday, May 14, 2012 - Post #30138
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1

Last Login: Yesterday @ 11:52 AM
Posts: 4,886, Visits: 22,781
The problem is Windows sends the question mark, so GenoPro cannot do anything.  I am sure you get the same problem on many Windows programs, especially those applications which are using code pages.

The only fix is creating a native Unicode version of GenoPro.  This task alone requires several months of work.


Similar Topics

Click to view RSS...
Expand / Collapse

Reading This Topic

Expand / Collapse
Active: 2 - 1 guest, 0 members, 0 anonymous.
Refresh
No members currently viewing this topic!