Bug 145854

beta2 has an entry but in latin script. I'm not prepared to handle things
like subscript consonants (yet).

Thanks for fixing this. And I think Latin script is fine here.

But I just tested beta2 and choosing Khmer does not show the expected result. The installation still starts in English!
I understand that changing the boot screen to Khmer is not possible because of lack of support for complex scripts but when the first installation screen shows up I expect a Khmer interface. 
Starting the installation in English and switching on the first screen to Khmer does work.
So I will open the bug again. 

Very strange. Looks like a YaST bug.

If 'Locale: km_KH' is in /etc/install.inf, YaST correctly skips the
initial language selection and sets language and timezone to Khmer but
still shows english texts. In fact, you don't get translations in _any_
language after that.

All works fine if you start with English and go through the initial language
dialog.

Maybe Khmer crashes YaST's translation engine? :-)

Reassigned to maintainer of yast2-country.

Created attachment 66169 [details]
y2log

Here's a y2log for enhanced debugging pleasure.

Steffen, are the files with translations in inst-sys?

> 006-02-02 18:44:31 <3> linux(8900) [bash] ShellCommand.cc(shellcommand):78 /usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or directory

Yes. If I abort and start yast again in English, everything works.

how do I set Locale to km_KH (not booting from CD) when Khmer is not in linuxrc menu?

Abort yast, edit /etc/install.inf, then run 'yast'.
Booting with lang=km_KH should work, too.

Reproduced; but I do not understand. 
yast2 language client doesn't change the language in UI when something was set in linuxrc, it is just skipped. Stefan, don't you have any idea?

Are we sure _we_ have Khmer in all the various tables etc. we are using for language support? IIRC there are several YCP files with maps for keyboard, timezone, etc.; I have no clue what happens if a language set by linuxrc isn't present there.

Stefan, of course yast2-country has Khmer in all its tables - it works on al other cases but setting from linuxrc. I'm asking how yast sets the language for installation when it actaully does _not_ use the yast2-counry API, which is this situation.

I can't find a problem in yast2-country, as I wrote, it just skips the language setting if it was set before.

Marcus, isn't there any problem in start scripts?

Maybe this is related to the absence of yast2-trans-km?

This is a wild guess, but I read this https://bugzilla.novell.com/show_bug.cgi?id=147927
and I thought I let you know. 

No, it's some problem of initialization; the Khmer works when set in running yast.

Marcus, could you comment?

I try to explain how this works:

1) Starting an installation will ask the user for its language.
2) According to this selection an entry in /etc/sysconfig/keyboard:KEYTABLE
   will be available later.

   PROBLEM: Khmer didn't have a console font and the kbd package didn't
            provide a Khmer map.gz file. The contents of KEYTABLE are
            undefined (default us)

3) The x11 suggestion is based on the contents of the KEYTABLE
   variable. SaX2 has a basic mapping table from console map to X11 map
   
   PROBLEM: In this case there is no mapping available because Khmer doesn't
            exist on the console. Default is "us"

My solution suggestion is to create a link for Khmer console map pointing
to us. For example:

   /usr/share/kbd/keymaps/i386/qwerty/khmer.map.gz -> us.map.gz

If this would exist I can add a new entry in my mapping table and if
someone can tell me how to setup a Khmer X11 keyboard I can address the
problem.

I think this is misunderstanding. There is not a problem with setting keyboard layout for Khmer, but that the installation didn't start correctly in Khmer when the language was set in the boot menu (=before yast). I asked you not because of keyboard but because of the startup scripts - I think the problem might be somewhere in this area.

the startup scripts didn't handle the language. I'm only exporting the
variables set by linuxrc. You can have a look to /var/log/YaST2/y2start.log
for details

I can't see anything wrong in yast, IMHO the problem must be before.

according to comment 17 it's something with startup scripts

No, this bug is not related to keyboard mapping.

As I already said the startup scripts doesn't do any critical lang
setup. See the following code:

  FirstStage/F04-language

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

#=============================================
# 4) set language environment
#---------------------------------------------
LANGUAGE=en_US
infofile=/content
if [ -f $infofile ];then
    LANGUAGE=`sed -n 's/^LANGUAGE \([^ ]*\)/\1/p' $infofile`
fi
if [ ! "$Locale" = "" ];then
    LANGUAGE=$Locale
fi
set_language_init
unset LC_CTYPE
log "\tLanguage set to: $LANG"

#=============================================
# 4.1) start unicode mode
#---------------------------------------------
export LANG
start_unicode

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

If /content is wrong or $Locale is not set a bug may occur but
both information come from another point not the startup scripts
The set_language_init function will assign LANGUAGE to LANG and
include the fbiterm check for Japanese.

The log file /var/log/YaST2/y2start.log tells you what LANG has been
set

well, it's certainly not a bug in linuxrc when yast can't set the language

Isn't the problem somewhere in the fonts? Mike, any idea?

No, Khmer fonts work fine.

Back to linuxrc: why there is no entry for Khmer in linuxrc menu? (contradictory to comment #2)?

The bootloader has an entry. linuxrc just passes the value on. linuxrc does
absolutely nothing with it except setting the 'locale' entry in install.inf,
so IMO adding an entry in linuxrc is pointless (same as for Hindi,
for example).

What is special for the installation with km_KH is that locale (?) error (see comment #6). This is called only to get list of available locales and doesn't affect the translation process - anyway, if I comment that call in yast, nothing changes. 
But it might be a sign that somehing deeper is broken... (?)

Ok, found the problem. Though there was a Khmer locale, it was missing
a Khmer utf8 locale. I've added it and now it works.

I can confirm that the problem is solved in beta9. I can choose Khmer now at the boot screen and get the Khmer interface. 
Strange is that the entry in the menu now is "km_KH"? Reason for a new bug report I guess :-(

I've fixed it. Strange, that noone noticed it. :-(