During the installation, in the second step in kernel loading, there is a missing letter in the message "Loading kernel" 117 #. Keep the three newlines! 118 #. txt_load_kernel 119 msgid "" 120 "Loading Linux Kernel\n" 121 "\n" 122 "\n" 123 msgstr "" 124 "ΦÏÏÏÏÏη ÏÎ¿Ï ÏÏÏήνα Linux\n" 125 "\n" 126 "\n" http://svnweb.mageia.org/soft/theme/mageia-gfxboot-theme/trunk/po/el.po?view=markup The missing letter is the first "Φ" as you can see on the screenshots. I tested it in Mageia 2 beta 3 i586 DVD , in virtualbox
Created attachment 2057 [details] The "Loading kernel" message in English
Created attachment 2058 [details] The "Loading kernel" message in Greek
I guess you can updates the fix yourself ?
Like , adding a space before the word ? I dont know how to fix this, and i dont understand why the first letter does nt appear.
Oh ok sorry :/ Anne, maybe an idea ?
CC: (none) => ennael1
See Also: (none) => https://qa.mandriva.com/show_bug.cgi?id=47425
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
That's NOT an installer bug. This is way before stage2 (or even stage1) is loaded. That's either a bug where mageia-gfxboot-theme did not carry the latest translations or a gfxboot bug.
CC: (none) => thierry.vignaudSource RPM: mageia-gfxboot-theme-4.4.5.4-2.mga2.src.rpm => mageia-gfxboot-theme
@enneal : Can you check if this is a error in the mageia-gfxboot-theme and report back. Roelof
CC: (none) => r.wobben
@dglent@free.fr: Since installer is now in current version 5beta1 there is a chance this bug has meantime been fixed. But maybe you are in the meantime able to propose a fix or patch for the bug yourself? Please review current status, if valid please change 'NEEDINFO' to '5beta1'. If fixed please close? Thanks v.m.
CC: (none) => i18n-bugs
I just tested the Mageia 4.1 DVD/x86_64 installer in a KVM VM and this issue is still there. I cannot see any similar issues elswhere at a first glance, but it seems that every other part of the installation process is generated in a completely different way from this specific message. I will test the Mageia 5b1 installer soon and let you know.
CC: (none) => thkala
Just tested the Mageia 5b1 DVD/x86_64 installer in a KVM VM - the issue exists in that version as well.
Hardware: i586 => All
Keywords: NEEDINFO => (none)Whiteboard: (none) => 5beta1
Using the command `gfxboot-font -s 16x16.fnt' for the font file contained in /boot/gfxmenu, it is possible to view the available font glyphs. That font file does _not_ contain a glyph for the capital Phi letter ('Φ'), which is the one missing from the message in question. It also seems to be missing a few other Greek letters (e.g. 'Î', 'Ψ', 'Ω', 'ζ').
I had a look at the latest mageia-gfxboot-theme package (4.4.5.18). The 16x16.fnt font file comes pre-bundled with the source tarball and is not rebuilt with the package. I verified that it does not contain the missing letter either. A new version of that file with the missing glyphs would fix this bug, but I was not able to build one successfully - I'm probably missing a few fonts from my system.
Thanks Theodoros, the fonts used are: http://svnweb.mageia.org/soft/theme/mageia-gfxboot-theme/trunk/fonts/Makefile?view=markup If i add the following, i have the missing "Φ" @@ -31,8 +31,11 @@ -f DejaVuSans-Bold:size=14:autohint=0 \ -f wenquanyi_12pt.pcf:size=16:bold=1 \ -f gulim:size=17:bold=1:nobitmap=1:autohint=1 \ + -p /usr/share/fonts/TTF/liberation/ \ + -f LiberationSans-Regular.ttf:size=14 \ 16x16.fnt >16x16.fnt.log rm -f tmp.txt clean: rm -f .ready *~ + [dglent@localhost fonts]$ gfxboot-font -s 16x16.fnt | grep Φ Char 0x03a6 'Φ' What would be the proper fix here?
By the way, this is the link to the Mandriva bug, from January 2009! " Missing letter in the greek version of "Loading Linux Kernel" " https://qa.mandriva.com/show_bug.cgi?id=47425 I don't remember if it was really fixes... Or was there some other change?
CC: (none) => 231036448
Keywords: (none) => PATCH
Still valid in Mageia 5, beta 3 .
looks something for atelier/graphic part
Assignee: bugsquad => atelier-bugs
Based on Dimitrios' input in comment 14, I had a look at the Makefile for the 16x16.fnt file, and it was relatively broken. It seems it can't find any of our fonts, so I had to add all paths manually. I also had to replace gulim and KhmerOS_sys which are not provided in Mageia. With this, I get a pretty complete font file which does contain Φ. Here is my patch: Index: mageia-gfxboot-theme-4.5.6.1/fonts/Makefile =================================================================== --- mageia-gfxboot-theme-4.5.6.1/fonts/Makefile +++ mageia-gfxboot-theme-4.5.6.1/fonts/Makefile 2015-02-23 00:24:32.789174693 +0100 @@ -1,5 +1,8 @@ GFXBOOT_FONT = gfxboot-font KEYMAPCHARS = gfxboot-keymapchars +FONTDIR = /usr/share/fonts +TYPE1DIR = $(FONTDIR)/Type1 +TTFDIR = $(FONTDIR)/TTF all: .ready @@ -17,6 +20,7 @@ -t tmp.txt \ -t ../src/main.log \ -t ../data-install/langs \ + -p $(TYPE1DIR)/hebrew:$(TTFDIR)/arabic/kacst:$(TTFDIR)/korean:$(TTFDIR)/bengali:$(TTFDIR)/dejavu:$(TTFDIR)/lohit:$(TTFDIR)/tamil:$(TTFDIR)/thai:$(FONTDIR)/google-noto:$(FONTDIR)/lklug:$(FONTDIR)/wqy \ -f NachlieliCLM-Bold:size=14:c=0x590-0x5ff \ -f KacstOne:size=14:c=0x600-0x6ff,0xfe70-0xfefc:dy=2 \ -f MuktiNarrow:size=18:c=0x0981-0x09fa:bold=1 \ @@ -27,10 +31,10 @@ -f lklug:size=17:c=0x0d82-0x0df4:bold=1:dy=1 \ -f Loma:size=17:c=0x0e01-0x0e7f:bold=0:dy=-2 \ -f Loma:size=17:c=0x0e81-0x0eff:bold=0:dy=-2 \ - -f KhmerOS_sys:size=16:c=0x1780-0x17f9:dy=-2 \ + -f NotoSansKhmer-Bold:size=16:c=0x1780-0x17f9:dy=-2 \ -f DejaVuSans-Bold:size=14:autohint=0 \ -f wenquanyi_12pt.pcf:size=16:bold=1 \ - -f gulim:size=17:bold=1:nobitmap=1:autohint=1 \ + -f UnDotum:size=17:bold=1:nobitmap=1:autohint=1 \ 16x16.fnt >16x16.fnt.log rm -f tmp.txt
CC: (none) => remi
I'll play around a bit more, trying to minimise the differences with the current font (I noticed that some dy offsets have become redundant, the previous log is pretty useful for that since I'm able to check the diff).
Assignee: atelier-bugs => remi
I did some further testing, and I realised that some fonts are not really necessary: - NachlieliCLM-Bold only brings a 5 hebrew characters which can also be provided by DejaVuSans-Bold - KhmerOS_sys was not used in the previous version, and NotoSansKhmer-Bold is not used either in my new version - KacstOne brings ~50 arabic characters, which can also be provided by DejaVuSans-Bold. If it looks good enough, it might be worth dropping KacstOne too. I also reduced the size of the lohit_pa font which caused some increase in the overall size of all characters compared to the previous gfxboot font. Now I have to test the changes live. Here is my current patch: Index: mageia-gfxboot-theme-4.5.6.1/fonts/Makefile =================================================================== --- mageia-gfxboot-theme-4.5.6.1/fonts/Makefile +++ mageia-gfxboot-theme-4.5.6.1/fonts/Makefile 2015-02-23 21:01:55.272294787 +0100 @@ -1,5 +1,7 @@ GFXBOOT_FONT = gfxboot-font KEYMAPCHARS = gfxboot-keymapchars +FONTDIR = /usr/share/fonts +TTFDIR = $(FONTDIR)/TTF all: .ready @@ -17,23 +19,19 @@ -t tmp.txt \ -t ../src/main.log \ -t ../data-install/langs \ - -f NachlieliCLM-Bold:size=14:c=0x590-0x5ff \ - -f KacstOne:size=14:c=0x600-0x6ff,0xfe70-0xfefc:dy=2 \ + -p $(TTFDIR)/bengali:$(TTFDIR)/dejavu:$(TTFDIR)/lohit:$(TTFDIR)/korean:$(TTFDIR)/tamil:$(TTFDIR)/thai:$(FONTDIR)/lklug:$(FONTDIR)/wqy \ -f MuktiNarrow:size=18:c=0x0981-0x09fa:bold=1 \ -f lohit_hi:size=18:c=0x0901-0x0970:bold=1 \ - -f lohit_pa:size=19:c=0x0a01-0x0a74:bold=1:autohint=1 \ + -f lohit_pa:size=17:c=0x0a01-0x0a74:bold=1:autohint=1 \ -f lohit_gu:size=18:c=0x0a81-0x0af1:bold=1 \ -f TSCu_Paranar:size=18:c=0x0b82-0x0bfa:dy=2:bold=1 \ -f lklug:size=17:c=0x0d82-0x0df4:bold=1:dy=1 \ - -f Loma:size=17:c=0x0e01-0x0e7f:bold=0:dy=-2 \ - -f Loma:size=17:c=0x0e81-0x0eff:bold=0:dy=-2 \ - -f KhmerOS_sys:size=16:c=0x1780-0x17f9:dy=-2 \ + -f Loma:size=17:c=0x0e01-0x0eff:bold=0:dy=-2 \ -f DejaVuSans-Bold:size=14:autohint=0 \ -f wenquanyi_12pt.pcf:size=16:bold=1 \ - -f gulim:size=17:bold=1:nobitmap=1:autohint=1 \ + -f UnDotum:size=17:bold=1:autohint=1 \ 16x16.fnt >16x16.fnt.log rm -f tmp.txt
I tested the changes with the grub theme (I could not confirm the fix of the issue in comment 0 since this one needs to be tested at install time). It looks like my new font set is working fine, and dropping KacstOne is a good thing since the DejaVuSans-Bold Arabic characters fit the rest much better than KacstOne did.
commit 374718e4eed2e5c30788170d987631baf129b4e6 Author: Rémi Verschelde <remi@...> Date: Mon Feb 23 21:46:46 2015 +0100 fonts: Rebuild 16x16.fnt to include missing glyphs and update existing ones This fixes among other things a long-running bug about missing glyphs for the Greek language (mga#5527) --- Commit Link: http://gitweb.mageia.org/software/design/bootloader-theme/commit/?id=374718e4eed2e5c30788170d987631baf129b4e6
This bug should be fixed in Mageia 5 RC with mageia-gfxboot-theme-4.5.6.2-1.mga5. I'll wait for confirmation (and hopefully there won't be regressions) before closing it.
The capital phi is still missing in the first round of Mageia 5 RC testing... :-/ I'll have to dig in some more.
Whiteboard: 5beta1 => 5rc
Thank you very much Rémi! to test it we will have to wait a new iso, right ?
(In reply to Dimitrios Glentadakis from comment #25) > Thank you very much Rémi! > > to test it we will have to wait a new iso, right ? Yes. I already tested the first round of RC ISOs that the QA team is working on, and sadly the bug does not seem fixed, even though Φ is included in the font now... I need to check with ennael if the installer's gfxboot theme does not use another font than the one I fixed, which might be limited to the grub theme of installed systems.
I've check the testing RC Live ISOs and the bug is actually fixed \o/ I'll have to check again the classical ISOs and see with Anne if they take their gfxboot font from another place.
Fixed in the classical ISOs too for Mageia 5 RC.
Status: NEW => RESOLVEDResolution: (none) => FIXED
This was a bug since 2009, thank you very much Rémi for having fixed it !