Re: non-i18n'd arches
On Sun, Mar 10, 2002 at 08:39:26PM -0600, Christian T. Steigies wrote: Should I commit the changes I needed to active UTF on m68k? Will it still work on VME? I don't know if there are similar problems on other arches, Tested on mvme166; as the vme boards only have serial console, the install dropped back to standard English install. No problems. Cheers, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Mon, 2002-03-11 at 02:39, Christian T. Steigies wrote: Should I commit the changes I needed to active UTF on m68k? Will it still work on VME? I don't know if there are similar problems on other arches, other video hardware, I only got one success report from a Mac quadra user. Is this enough testing for this change? Yeah, I think so. It might be worth a quick grep in drivers/video to see if there are any others that set fix-line_length wrongly. Does m68k build separate rootdisk images per subarch, or is there just one that gets shared? If they are different, you can disable LC for individual machine types if that turns out to be necessary. If there is no fbcon support at runtime it will automatically fall back to the non-i18n version, which should take care of VME for example. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Sat, 2002-03-09 at 01:27, Christian T. Steigies wrote: So, the framebuffer on my amiga is special? I was told it works on a mac... Special is one word for it. :-) What does fbset say if you run it on the Amiga? It sounds like your framebuffer is reporting its geometry or something in a way that bogl doesn't understand. I don't know if anybody has used bogl on a machine with planar graphics before, so there might be issues there. The mac uses packed pixels from what I remember. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Sat, 2002-03-09 at 18:04, Christian T. Steigies wrote: Planar grafics? This is using a grafic card, I could try without, using native video if you think that helps. It's worth a try. We might at least learn something. What driver does your card use? I guess the native one is amifb.c, right? p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Fri, 2002-03-08 at 15:00, Christian T. Steigies wrote: The boot-floppies on amiga usually boot in 640x480, but I just tried 1024x768, some thing. Maybe is related to the Penguin in the top left corner which is not deleted? The non-UTF boot-floppies always cleared the screen so that the penguin was gone when the welcome screen came up. No idea how this looks on a mac though. The screen should definitely be cleared. 640x480 is the default resolution on i386 so you oughtn't to have a problem there. Can you try running bterm on its own and see if it works at all for you? p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Fri, 2002-03-08 at 16:50, Christian T. Steigies wrote: On Fri, Mar 08, 2002 at 04:42:31PM +, Phil Blundell wrote: Can you try running bterm on its own and see if it works at all for you? Does that work on a console? cts@lepjas2:~bterm Usage: bterm -f font.bgf [ -l locale ] [ program ] Oh no... my F key works only by use of massive violence, is there a chance that it works in an xterm via ssh login without a properly configured X? What font do I give it? You can't run bterm over X, it needs to use the console. The font file is utilities/bogl/unifont-reduced.bgf in your boot-floppies build tree. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Fri, Mar 08, 2002 at 06:17:46PM +, Philip Blundell wrote: On Fri, 2002-03-08 at 16:50, Christian T. Steigies wrote: On Fri, Mar 08, 2002 at 04:42:31PM +, Phil Blundell wrote: Can you try running bterm on its own and see if it works at all for you? Does that work on a console? cts@lepjas2:~bterm Usage: bterm -f font.bgf [ -l locale ] [ program ] Oh no... my F key works only by use of massive violence, is there a chance that it works in an xterm via ssh login without a properly configured X? What font do I give it? You can't run bterm over X, it needs to use the console. The font file is utilities/bogl/unifont-reduced.bgf in your boot-floppies build tree. Same thing... the cursers moves over the top of the screen, I line is drawn in the topmost row of the screen, I can see the one row of the cursor flashing, when I type something this flashing cursor moves to the right, but it never leaves the topmost line, even when I execute commands that produce a lot of output (ls -l). So, the framebuffer on my amiga is special? I was told it works on a mac... Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Sun, Mar 03, 2002 at 09:21:14PM +, Philip Blundell wrote: [..snip..] The only requirements I can think of are: - framebuffer support in your kernel (should be no problem for m68k) There's no fb support on mips ip22 and and it most likely won't be implemented in the near future. This throws out mips, i fear. -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Thu, 2002-03-07 at 14:54, Guido Guenther wrote: On Sun, Mar 03, 2002 at 09:21:14PM +, Philip Blundell wrote: [..snip..] The only requirements I can think of are: - framebuffer support in your kernel (should be no problem for m68k) There's no fb support on mips ip22 and and it most likely won't be implemented in the near future. This throws out mips, i fear. Do you mean there is no fb support on _any_ mips, or just on one subarchitecture? If the latter, you can still use LANGUAGE_CHOOSER on the subarches that do have fbcon. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Thu, Mar 07, 2002 at 03:19:50PM +, Phil Blundell wrote: On Thu, 2002-03-07 at 14:54, Guido Guenther wrote: On Sun, Mar 03, 2002 at 09:21:14PM +, Philip Blundell wrote: [..snip..] The only requirements I can think of are: - framebuffer support in your kernel (should be no problem for m68k) There's no fb support on mips ip22 and and it most likely won't be implemented in the near future. This throws out mips, i fear. Do you mean there is no fb support on _any_ mips, or just on one subarchitecture? If the latter, you can still use LANGUAGE_CHOOSER on the subarches that do have fbcon. IP22 is currently the only supported subarch on big endian mips machines, since none of the mips porters has access to something else. -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Thu, 2002-03-07 at 15:21, Guido Guenther wrote: IP22 is currently the only supported subarch on big endian mips machines, since none of the mips porters has access to something else. I see. In that case, you're right, there is no point in turning on i18n for mips at the moment. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
Christian T. Steigies [EMAIL PROTECTED] cum veritate scripsit: My X is not working yet, but I got positive feedback from a Mac Quadra 840AV user. Everything (well, he did not complete the installation and tested only english, but: I saw the different languages pop up. Maybe I'll try the Spanish version.) seems to work, at least on Macs. Now if somebody could tell me, why it is not working for me... Does amiga have different screen width ? regards, junichi -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Wed, 2002-03-06 at 04:58, Christian T. Steigies wrote: I tried it on my amiga, it does not seem to work. All the output (blue background with window, text et all) seems to be scrolled through the first line of the display, all the other lines remain empty. Until I switch to the second console and back, then all lines except the first are identical to the contents of the second console. I've never seen that before. It sounds like either bterm or slang-utf8 is broken on your system for some reason. Can you try to isolate the problem to one or the other? For example, run dbootstrap-lc inside an xterm -u8 and see if it works then. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Mon, 2002-03-04 at 01:34, Richard Hirst wrote: So, for vme, there will be no frame buffer support in the kernel. Does having lang chooser turned on then present a problem, or will it just drop back to something sensible? It'll fall back to an English installation. Serial console is supported on i386 too. The only time you wouldn't want to turn LANG_CHOOSER on would be on architectures that don't ever support framebuffer. For ia64 and hppa, there will be frame buffer support in the kernel, but (for hppa, anyway) it might not support the particular h/w. Also the install might be done via serial console. Will lang chooser drop back to something sensible in those cases too? Yup. Again, the hardware doesn't support fbcon situation applies to i386 too, depending on your particular video card. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Mon, 2002-03-04 at 21:37, Christian T. Steigies wrote: On Sun, Mar 03, 2002 at 08:53:13PM -0800, Christian T. Steigies wrote: I'll try to build without cfdisk-utf8 for m68k... that seems to work, but: E: rootatari.bin is larger than root1440atari.bin (1495947 1474560) E: ./rescue.sh abort I assume this is due to UTF since I have never had this before. Any hints? The easy fix is to reduce the number of languages you ship on the root disk. This is set in the config file. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Sun, Mar 03, 2002 at 07:48:00PM +, Philip Blundell wrote: I see that sparc, mips, hppa and m68k have not yet enabled the LANGUAGE_CHOOSER. Is there any particular reason for that? It would be good to have i18n on as many architectures as possible by the time we release. I just turned it on in ia64, and it is basically working. Relative to my previous non-i18n build, I see these problems: 1. Ugly borders to dialog boxes, using +-| rather than graphics chars. (this on vga, not on serial). This is a real shame, the installer was looking pretty smart in my non-i18n build. I'm assuming other i18n enabled archs have this same problem... 2. Doesn't always redraw the screen. e.g. mke2fs output overwrites the the display without clearing first, and previous dialog box is sometimes visible round the endges of the current one. (this with French, not with English). 3. The french message Installer le systeme de base - alt-F4 pour deboguer, alt-F1 p is too long to fit the top of the dialog box. I did vga installs in French, English, and Janpanese, and a serial install in English. The serial install worked just like the non-i18n install, didn't offer language choice, used nice graphics chars for borders. No idea what the Janpanese one was saying to me, but the screen layout, line lengths, etc looked like it might be working ok. I used the i386 language set, although I guess I could use more on ia64 as there is no real space constraint. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Mon, 2002-03-04 at 22:58, Richard Hirst wrote: 1. Ugly borders to dialog boxes, using +-| rather than graphics chars. (this on vga, not on serial). This is a real shame, the installer was looking pretty smart in my non-i18n build. I'm assuming other i18n enabled archs have this same problem... Yup. This is caused by legacy newt/slang/termcap problems. From what I remember there is an assumption somewhere that the line drawing characters are only a single byte, whereas a two-byte sequence is needed for UTF8. Unfortunately I think we just have to live with it for the time being. 2. Doesn't always redraw the screen. e.g. mke2fs output overwrites the the display without clearing first, and previous dialog box is sometimes visible round the endges of the current one. (this with French, not with English). There's an important bug open for this already. I don't know the number off the top of my head, but the title is something obvious like dbootstrap: screen not cleared. I used the i386 language set, although I guess I could use more on ia64 as there is no real space constraint. Yup. ARM does the same. You can set the language list to whatever you want, though it would be a good idea to check the stats to make sure the translations you're including aren't desperately stale. Having an install that is only half translated would make for a pretty miserable user experience. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Sun, Mar 03, 2002 at 07:48:00PM +, Philip Blundell wrote: I see that sparc, mips, hppa and m68k have not yet enabled the LANGUAGE_CHOOSER. Is there any particular reason for that? It would be good to have i18n on as many architectures as possible by the time we release. Speaking for m68k, its not enabled, because I never heard about that (not consciously at least). Whats the impact, do we need extra packages, more documentation or is it just one switch and everything works? Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Sun, 2002-03-03 at 20:51, Christian T. Steigies wrote: On Sun, Mar 03, 2002 at 07:48:00PM +, Philip Blundell wrote: I see that sparc, mips, hppa and m68k have not yet enabled the LANGUAGE_CHOOSER. Is there any particular reason for that? It would be good to have i18n on as many architectures as possible by the time we release. Speaking for m68k, its not enabled, because I never heard about that (not consciously at least). Whats the impact, do we need extra packages, more documentation or is it just one switch and everything works? The only requirements I can think of are: - framebuffer support in your kernel (should be no problem for m68k) - packages like libnewt-utf8-0 need to have been built for your architecture Other than that, it should just be a case of adding m68k to the list of architectures in this part of the config file: # whether to use the language chooser in dbootstrap for kernel flavours that # support it, `true' or `false' ifneq (,$(filter $(architecture),i386 arm powerpc alpha)) export USE_LANGUAGE_CHOOSER := true export LC := true else export USE_LANGUAGE_CHOOSER := false export LC := false endif You used to have to edit rootdisk.sh as well but it looks like that is no longer the case. Try it and see how you get on; I expect it will just work. You may also want to tailor the list of included languages a bit further down in config, depending on how much space you have available in your root image. By default you will get the same top ten that i386 uses. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
Philip Blundell [EMAIL PROTECTED] cum veritate scripsit: I see that sparc, mips, hppa and m68k have not yet enabled the LANGUAGE_CHOOSER. Is there any particular reason for that? It would be good to have i18n on as many architectures as possible by the time we release. It would be nice to have it enabled, and get it tested, so that we know it won't be too painfully slow. regards, junichi -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Sun, Mar 03, 2002 at 09:21:14PM +, Philip Blundell wrote: The only requirements I can think of are: - framebuffer support in your kernel (should be no problem for m68k) Quite a problem for the various m68k vme boards, which are all serial console only (mvme16x, bvme6000, mvme147 subarchs). Also on hppa we have some machines that have the equivalent of vga console, but no frame buffer support yet. ia64 and hppa support serial as well as 'vga' installs. So, for vme, there will be no frame buffer support in the kernel. Does having lang chooser turned on then present a problem, or will it just drop back to something sensible? For ia64 and hppa, there will be frame buffer support in the kernel, but (for hppa, anyway) it might not support the particular h/w. Also the install might be done via serial console. Will lang chooser drop back to something sensible in those cases too? Cheers, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Mon, 4 Mar 2002 01:34:00 + Richard Hirst [EMAIL PROTECTED] wrote: For ia64 and hppa, there will be frame buffer support in the kernel, but (for hppa, anyway) it might not support the particular h/w. Also the install might be done via serial console. Will lang chooser drop back to something sensible in those cases too? Choosing English in Language-chooser should work. Or configuring the serial terminal emulator to support UTF-8 strings. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-i18n'd arches
On Mon, Mar 04, 2002 at 11:43:23AM +0900, Junichi Uekawa wrote: On Mon, 4 Mar 2002 01:34:00 + Richard Hirst [EMAIL PROTECTED] wrote: For ia64 and hppa, there will be frame buffer support in the kernel, but (for hppa, anyway) it might not support the particular h/w. Also the install might be done via serial console. Will lang chooser drop back to something sensible in those cases too? Choosing English in Language-chooser should work. Or configuring the serial terminal emulator to support UTF-8 strings. Please see Bug#136717, utf (currently ) requires cfdisk-utf8, which does not build for m68k without patches. But even then it does not seem to work. I'll try to build without cfdisk-utf8 for m68k... Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
