localizing in Russian without unicode

[Pocus]

I'm stuck in using Dx8 for now, I'm using Omega for Dx8. I would like to go to Asphyre, but I don't have quite the time to do the conversion.

I can change in the D3DFont.pas the occurences of 126 to 255, if this is the only problem I can encounter, its not a big deal.

For now my regional settings are set to my country, France.

Can I ask you where to find charset 1251 true types font? A search on the web returns various pages on how to "russify" an app, but its far from being clear which fonts are not unicode and contains the cyrillic chars in part 127+.

Sorry to ask that, this is not I don't want to do the search, but I just need 2 files, one arial and one smallfonts, but in 1251 format and it should be ok. If you have them under the hand, I would really appreciate a forward.

Thanks you all for your input.

[Clootie]

I'm not aware where to find pure cyrillic truetype fonts. For combined fonts look here: http://www.alanwood.net/unicode/fonts.html.
But I can send you cyrillic FON (raster font) from mine system if you wish (mail me directly).
Other way to experiment is to use combined font and set windows locale to russian.

[dmantione]

As far as I know most standard fonts shipped with Windows can do Cyrillic. You don't need to search for a specific Cyrillic truetype font, but one that contains Cyrillic glyphs and a codepage 1251 table.

[Clootie]

And that's the problem for him: if Windows have different locale and he tries to render text containing chars from upper 128 elements of single byte table - he will definitely get wrong output with standart fonts (even if one contains cyrillic glyths)...

[Pocus]

I will mail you, if raster fonts can be used instead of TTF, I don't really care

Thanks all for your patient answers.

[Clootie]

Another note -
In d3dfont.pas you can modify:
[pascal] pFont := CreateFont(nHeight, 0, 0, 0, dwBold, dwItalic,
0, 0, DEFAULT_CHARSET, OUT_DEFAULT_PRECIS,
CLIP_DEFAULT_PRECIS, ANTIALIASED_QUALITY,
VARIABLE_PITCH, @m_strFontName);[/pascal]
And replace DEFAULT_CHARSET with RUSSIAN_CHARSET (or some other). This should allow you to use cyrillic glyths even then windows locale set to different one.
So can just update your windows copy with "extended fonts" via language control panel with combined unicode fonts and still draw single byte ASCII sequences.

[Pocus]

I got your font Clootie.

Made a serie of tests. Nothing work.


I tried with or without changing DEFAULT_CHARSET to RUSSIAN_CHARSET.

I tried with or without changing my local setting from French to Russian.

With Lucida Sans Unicode or with your font, either I get my text in western character (my strings are really western characters but I thought they would be remaped to their equivalent index in the cyrillic charset), or I do not get any text.


-----------------

Just to be sure I understand the logic: a russian person localizing text can save cyrillic chars in ANSI format (using a 1251 charset). This appears as Cyrillic to him, but for an english windows, it will be displayed as western letters.

This work like this: if the english person uses a 1251 charset table, a mapping is done, for example character 230:

"f" => "Ф", # xE6 230 x424 1060 xD0A4 CYRILLIC CAPITAL LETTER EF

is displayed in the text file (english windows) as a "f". it is displayed as a "Ф" in russian windows.

it is supposed to be shown as "Ф", index 230, with an 1251 charset table.

Well, I'm right?

It don't work for now though

[dmantione]

First, compare

http://en.wikipedia.org/wiki/Code_page_1252

... and ...

http://en.wikipedia.org/wiki/Code_page_1251

The Ф can be found at position D6, not E6 in codepage 1251. At position D6 in codepage 1252, you will see an ?ñ. So, the Ф will appear in a machine configured for a western font as ?ñ, not f, there exists no automatic transliteration.

[Clootie]

dmantione is 100% right - there will be no automatic transliteration.

Example of text file you'll probably get from translator: http://www.frei.ru/golos/chat/100798.txt (this seems to be a log from a chat program)

[EAST]

For Enigma we did translations into 6 languages including Russian, Polish and Hungarian.

In all cases we rasterized a cyrillic font set mapped to a Russian (or Polish, Hungarian) keyboard.

All text for the game was in a localization file and indexed. We used native language speakers (from fansites no less) to localize line by line. It was largely voluntary, some cost, but much better results than the localization company did with the original translations.

We had 10000+ lines of text and it worked well.