Promjena u regional settings (language) iz koda?

Srki_82: Oslanjanje na podesavanja u Regional Settings-u nije bas najbolje resenje. Mi smo u firmi imali dva programa od kojih je jedan zahtevao americka podesavanja, a drugi srpska. Prilicno je smaralo to sto sam morao na jednom racunaru da pokrenem jedan, a na drugom drugi program da bih mogao istovremeno da radim u oba.

Srki_82: Zasto ne koristis unicode kontrole, a datum, vreme, realne brojeve i slicno prevodi sa svojim podesavanjima koje korisnik moze da bira u opcijama programa (naravno, to moras da napravis)?

Srki_82: Za jezik koji ce tvoj program koristiti mora unapred pre pokretanja programa da se podese opcije u control panelu tako da tvoj program ne moze to sam da uradi.

AppLocale is based on the new application compatibility technology introduced in Windows XP. It can only be installed on Windows XP (Home or Pro) or Windows 2003 Server. Please note that AppLocale setup requires administrator rights to the system since some system component files are being installed.

The AppLocale setup program installs the following files on your system under %SystemRoot%\AppPatch directory:

- readme.rtf This file
- apploc.exe The AppLocale applet used to launch the target application
- alres***.dll The localized resource files for the AppLocale applet
- alLayer.dll AppLocale specific application compatibility engine
- .Custom\{deb7008b-681e-4a4a-8aae-cc833e8216ce}.sdb AppLocale engine application database

Because of the nature of AppLocale’s implementation and because each application is unique in the way it handles text data, AppLocale might cause application-specific side-effects and limitations that the user would not experience once the "system locale" is properly set. Some of these application-specific side-effects and limitations may be:

- Setup programs: for some for setup programs that require a reboot, it is strongly suggested to properly set the system locale to match the language of the target application during the installation.

- Server application: non-Unicode server applications have not been tested and are not supported by AppLocale.

- 16-bit application are not supported by AppLocale.

- Input Method Editors (IME) might not properly function in some private or owner drawn edit controls.

- File system support: creating localized file names or installing applications in localized folder names that do not match your system locale might result in broken functionality.

- Even after applying AppLocale some of the application’s user interface might not render properly. This should not cause any functionality breaking and it is related to the application’s specific way of handling non-Unicode data.

- Running Unicode applications or applications that handle their own character encoding conversions (e.g. Internet Explorer) in AppLocale compatibility mode might result in unexpected results and breaking functionality.

savkic:
Koji Delphi koristiš, kako praviš menije (TMenu, TPopupMenu ili...), koji font koristiš za edit kontrole i na kojim sistemima će se tvoj program izvršavati?

Srki_82: Deo teksta sa http://www.microsoft.com/globaldev/tools/apploc.mspx

Application developers should not consider AppLocale as an alternative to migrate their product to Unicode. Today, with Microsoft Layer for Unicode (MSLU), creating pure Unicode applications that can also be deployed on non-Unicode platforms - such as Windows 98 - has been made possible.

Cak i Microsoft koji je napravio AppLocale preporucuje da se ovaj program ne koristi, nego da se koriste Unicode kontrole, ali ti radi kako mislis da je najbolje.

JaHvram: Stvarno ne znam zasto ne koristis UTF-8 kontrole (TNT kontrole)? Da li imas neki poseban razlog ili ne? I ja sam ih prvo izbegavao, a onda sam skontao da su one najbezbolnije resenje barem sto se korisnika tice, a oni su valjda najvazniji ;)

delalt: Ma nemam nikakav poseban razlog da ne koristim TNT kontrole, svi kažu da su dobre,
gore sam objasnio da bi u neke starije programe trebalo samo dodati mogućnost lokalizacije.
Oni se kao takvi neće dalje razvijati, pa mi je izmjena svih postojećih komponenti
malo veći posao. Ono mi se učinilo najjednostavnije i najbrže.

This expert does everything it can to preserve and map properties and can handle all of the basic types such as integers, strings, and enums. It can also handle many more complex properties such as component references, TStrings, TFields, properties that support calling TPersistent.Assign between each other (such as TFont/TBitmap), and conversions between properties of slightly differing but largely compatible types such as TStrings to a string and conversions between various ordinal types, within the limitations of the RTTI GetPropValue and SetPropValue functions. You will generally be able to map from ordinals to floats to strings, for example, but mapping from strings to integers might raise errors if the string does not represent an integer.