Re: [Freedos-devel] Do FreeDOS in the Cloud

2019-01-02 Thread Jerome Shidel


> On Jan 2, 2019, at 4:05 PM, stecdose  wrote:
> 
> 
>>> * If the installation language is Russian, the text is garbled, no
>>> Cyrillic letters are displayed.
>> Yeah, that’s a known issue. Cant really think of a “good” way to solve it.
>> 
>> Here’s the problem.
>> 
>> Language and translation change when that language is highlighted on the 
>> menu. However, the Language settings, Codepage and font are not set until 
>> that language is actually selected.
>> This requires loading some TSRs. They may be a way to unload them. But, I 
>> don’t know if or what it is.
>> 
>> I have a bunch of stuff I’ve written over the years that can load fonts. 
>> Most recently are the QFONT tools included with PGME. They can convert 
>> to/from simple bit fonts, load qfonts temporarily, or turn them into a TSR. 
>> I may do something there to temp load/unload the Russian font on the menu.
> 
> Maybe storing the codepage and font information are stored along with the 
> langua/keyboard layout is good.
> 
> This way a small utility ("loadfont") can be called when changing language. 
> This would be good for all languages that have special letters.

Not a bad idea. But, not necessary. FDI is already designed to run a language 
specific SETLANG.BAT that has any settings and programs needed for a selected 
language. 

The issue is switching temporarily to highly different possibilities prior to 
selection. More specifically, unloading settings made from the previous 
highlight. 

Mostly,it is not an issue for most of the languages supported by FDI. However, 
Russian requires it.

So, each time you scroll onto and off of the language, you would end up loading 
one codepage on top of another, and another and another.

As a native English speaker, I really never had to mess around with those. 
There may be a way to unload one. But I am unaware of it. I don’t have the time 
or desire to RTFM it. 

It would just be quicker and easier to just extract the required fonts from 
their codepage, convert to my QFONT format, and use my loader to temporary load 
any font using no TSR or memory. 

That solution has one drawback, either limit fonts to only EGA or VGA sizes... 
Or, provide two sets for each language and detect/select the appropriate one.

> 
>> 
>> I still need to do some more work in FDI to be able to handle installation 
>> from LiveCD-Type2.
>> 
>> LiveCD-Type1 is mostly ready. My plan is to put both to the Devs and 
>> Community to decide which will be the LiveCD.
>> 
> Looking forward to it :)
> 

:-)

> 
> Nils
> 

Jerome


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] Do FreeDOS in the Cloud

2019-01-02 Thread stecdose



* If the installation language is Russian, the text is garbled, no
Cyrillic letters are displayed.

Yeah, that’s a known issue. Cant really think of a “good” way to solve it.

Here’s the problem.

Language and translation change when that language is highlighted on the menu. 
However, the Language settings, Codepage and font are not set until that 
language is actually selected.
This requires loading some TSRs. They may be a way to unload them. But, I don’t 
know if or what it is.

I have a bunch of stuff I’ve written over the years that can load fonts. Most 
recently are the QFONT tools included with PGME. They can convert to/from 
simple bit fonts, load qfonts temporarily, or turn them into a TSR. I may do 
something there to temp load/unload the Russian font on the menu.


Maybe storing the codepage and font information are stored along with 
the langua/keyboard layout is good.


This way a small utility ("loadfont") can be called when changing 
language. This would be good for all languages that have special letters.




I still need to do some more work in FDI to be able to handle installation from 
LiveCD-Type2.

LiveCD-Type1 is mostly ready. My plan is to put both to the Devs and Community 
to decide which will be the LiveCD.


Looking forward to it :)


Nils



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] Do FreeDOS in the Cloud

2019-01-02 Thread Jerome Shidel
Hi,

> On Jan 2, 2019, at 12:38 PM, thraex  wrote:
> 
> 
> 2.01.2019 02:30 tarihinde Jerome Shidel yazdı:
>> 
>> Sorry, I didn’t notice. Displaying the found translations is a new feature 
>> in the build environment. I know there are a couple missin from the German 
>> translations. So, I figured it might be nice that you were shown during that 
>> phase.
> 
> Good idea indeed, thank you. I noticed that XDEL had neither French
> nor Turkish translations and that FDIMPLES was machine translated in
> these two languages therefore I added these translations to the archive
> containing CuteMouse files, so forget about the previous link, just
> download them all from
> .

Will do

> 
>>> I managed to build it locally with Fedora 28 in VirtualBox thanks to
>>> your video. That said, I noticed several problems, just to bring them to
>>> your attention:
>> 
>> Neat eh? Super easy to build one. :-)
> 
> :-)
> 
>>> * When I choose Turkish in the installer, some letters are changed, for
>>> instance ı becomes an i, ğ becomes a g, ş becomes an s. The text is
>>> still legible and understandable though.
>> 
>> I think that may be my fault. The I’ve been unable to figure out what DOS 
>> character set is correct in BBEdit. So, it refuses to save them unless I 
>> change them. I had to do a bunch of adjustments to frame sizes and line 
>> breaks for all of the translations so they displayed properly.
>> 
>> If you fix them in the versions that are in the source tree, I can update 
>> them so they aren’t mangled. Just avoid any changes that would require me 
>> needing to adjust them.
> 
> The problem is worse than I thought: even after the installation the
> charset problem remains, and it also affects characters like İ. Let's
> see what we can do when you get back on FreeDOS 1.3.

Hmmm. 

> And just so that I don't forget it, when the chosen keyboard in the
> installer is the French layout, I get the Spanish one (I think) instead.
> I have to type mkeyb fr after the installation to get the correct AZERTY
> layout.

It could be a minor bug in FDI or build process that may have occurred when I 
incorporated the Russian translations. 

> 
>>> * A ver command returns the following:
>>> FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
>>> whereas FreeCOM 0.84-pre6 has been released in September (see
>>> ). Wouldn't it make sense to
>>> use this more recent version?
>>> 
>>> That's all for now, as I couldn't install FreeDOS 1.3 Beta. Hopefully
>>> when I'm able to install I'll have more stuff to bother you with. :-P
>> 
>> If you would like a pleasant surprise... run
>> make cdrom release
>> :-)
> 
> Hey that's a neat FreeDOS 1.3 Beta LiveCD! :) If anyone wants to play
> with it, it can be downloaded from .
> The corresponding md5 sum is "177a9f511a664a5a51d2d749b0f753bf" and the
> sha256 sum is
> "f0d2ef4d00ce24049ef60107326071061701db0bea1b1a284901817c5969afd4". It
> installs just fine in AQEMU

There are a couple final touches I need to make to LiveCD-Type 1 and was going 
to wait until both Type1 & 2 were ready before having everyone play around with 
them. But, it’s ok. Everyone is welcome to start playing with LiveCD Type-1. 

Using the LiveCD part requires 128mb ram at present.

Also, There are a couple known bugs and unresolved issues at preset. This is 
early beta. 

Live portion will get installer eventually and probably automatic networking 
support under VirtualBox and VMware.

One main issue is under VirtualBox, the installer will complain about not being 
supported and drop out. Easy fix when I get to it. But, for now, after that 
happens, just relaunch it manually with setup.bat

Jerome


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] Do FreeDOS in the Cloud

2019-01-02 Thread thraex

2.01.2019 02:30 tarihinde Jerome Shidel yazdı:
> 
> Sorry, I didn’t notice. Displaying the found translations is a new feature in 
> the build environment. I know there are a couple missin from the German 
> translations. So, I figured it might be nice that you were shown during that 
> phase.

Good idea indeed, thank you. I noticed that XDEL had neither French
nor Turkish translations and that FDIMPLES was machine translated in
these two languages therefore I added these translations to the archive
containing CuteMouse files, so forget about the previous link, just
download them all from
.

>> I managed to build it locally with Fedora 28 in VirtualBox thanks to
>> your video. That said, I noticed several problems, just to bring them to
>> your attention:
> 
> Neat eh? Super easy to build one. :-)

:-)

>> * When I choose Turkish in the installer, some letters are changed, for
>> instance ı becomes an i, ğ becomes a g, ş becomes an s. The text is
>> still legible and understandable though.
> 
> I think that may be my fault. The I’ve been unable to figure out what DOS 
> character set is correct in BBEdit. So, it refuses to save them unless I 
> change them. I had to do a bunch of adjustments to frame sizes and line 
> breaks for all of the translations so they displayed properly.
> 
> If you fix them in the versions that are in the source tree, I can update 
> them so they aren’t mangled. Just avoid any changes that would require me 
> needing to adjust them.

The problem is worse than I thought: even after the installation the
charset problem remains, and it also affects characters like İ. Let's
see what we can do when you get back on FreeDOS 1.3.

And just so that I don't forget it, when the chosen keyboard in the
installer is the French layout, I get the Spanish one (I think) instead.
I have to type mkeyb fr after the installation to get the correct AZERTY
layout.

>> * A ver command returns the following:
>> FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
>> whereas FreeCOM 0.84-pre6 has been released in September (see
>> ). Wouldn't it make sense to
>> use this more recent version?
>>
>> That's all for now, as I couldn't install FreeDOS 1.3 Beta. Hopefully
>> when I'm able to install I'll have more stuff to bother you with. :-P
> 
> If you would like a pleasant surprise... run
> make cdrom release
> :-)

Hey that's a neat FreeDOS 1.3 Beta LiveCD! :) If anyone wants to play
with it, it can be downloaded from .
The corresponding md5 sum is "177a9f511a664a5a51d2d749b0f753bf" and the
sha256 sum is
"f0d2ef4d00ce24049ef60107326071061701db0bea1b1a284901817c5969afd4". It
installs just fine in AQEMU (but not in VirtualBox).


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] Do FreeDOS in the Cloud

2019-01-02 Thread Jim Hall
Hi

Github pages aren't working for me at the moment, but maybe that's a
network resolution problem on my end? I'm looking for release notes or
similar that I could use to announce your  updated gcc-ia16 toolchain on
the FreeDOS website. Or should I just use the notes you included here:

On Tue, Jan 1, 2019 at 7:08 AM TK Chia  wrote:

> Hello all,
>
> >> On my end, I have tweaked my gcc-ia16 toolchain build files, to avoid
> multi-line descriptions in the .lsm's for now.  I guess though that it is a
> bit late into the FreeDOS 1.3 release schedule to have this change
> included...
> > The 1.3 release is a little behind schedule and RC1 hasn’t shipped yet.
> Once it does, from that point on, only bug fixes for the release will be
> made. So, you update may make it into 1.3. After all, it’s a (not really)
> “bug fix” and not a new package.
>
> Thank you!  I have uploaded new packages for the gcc-ia16 toolchain, at
> https://github.com/tkchia/build-ia16/releases/tag/20190101 .
>
> Besides fixing the package descriptions to make them fit onto single
> lines, I have also included in the packages some compiler optimizations
> and other minor features that I recently implemented.
>
> I look forward to trying out the FreeDOS 1.3rc1 distribution.
>
> Thank you!
>
> --
> https://github.com/tkchia
>
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel