Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #11151
| From | Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: Use of virtual keyboards within a VO application, whether DBFs can contain non-English text |
| Date | 2017-11-17 16:49 +0100 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <oun0e7$s1t$1@gioia.aioe.org> (permalink) |
| References | <cd97cd4f-a72a-4886-bc7e-0a5dd9049bfe@googlegroups.com> |
Hi Tom,
you can test nearly everything on your own using the clipboard instead
of the keyboard. I assume that you use computers that have at Windows XP
or newer.
The following characters are the so called "ANSI" characters. It is the
latin 1 code page that Windows normally used for representing the
characters from chr (0) to chr(255).
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖרÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ
Spanish, French, German, Danish and other western european languages use
only characters from this selection. If you can copy these characters
into your program and the program can process them correctly, then
everything is ok.
For all other languages normally Unicode is needed. There are some
exceptions with languages like Russian where also solutions with code
pages exist. This depends also on the computer settings.
VO programs and the GUI classes and the DBF in general do not support
Unicode. It is much work to add some Unicode possibilities. It may be
necessary to make new applications in X# using Windows forms or WPF and
databases that support Unicode.
Arabic and Hebrew give additional very much work because of the
difficult right to left treatment. Every dialog, every output should
support right to left.
Arne Ortlinghaus
INFOMINDS AG
TomYale wrote:
> This is an interesting problem which may require the assistance of a non-English-speaking VO developer.
>
> I will be designing an application which requires a user to be able to enter text in languages that have either accented letters (as in the case of Spanish or French) or non-Latin letters or characters (as in the case of Arabic, Japanese or Chinese).
>
> Though I hadn't tested whether virtual keyboards insert non-English letters into an application of my own creation (my Esperanto virtual keyboard no longer works on my PC for some reason), I wish to explore two possibilities:
>
> 1) whether the application can switch to typing in Unicode characters into a new class inheriting from SingleLineEdit from a predetermined virtual keyboard pattern, coded into a keyDown event for the inheriting class, switching back and forth depending on which edit control has focus, or if this is not possible
>
> 2) whether the user can otherwise manually switch between keyboards they have installed on their PC, and the characters can still be entered and will appear in normal SingleLineEdit controls.
>
> The purpose will be to access data from DBF tables which will contain text in languages other than English, which I'm not sure is possible either.
>
> Any assistance into this somewhat unique problem will be greatly appreciated.
>
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Use of virtual keyboards within a VO application, whether DBFs can contain non-English text TomYale <thomasyale7110@gmail.com> - 2017-11-16 23:09 -0800 Re: Use of virtual keyboards within a VO application, whether DBFs can contain non-English text Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> - 2017-11-17 16:49 +0100 Re: Use of virtual keyboards within a VO application, whether DBFs can contain non-English text D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-11-21 01:07 +0100
csiph-web