Re: [Freedos-devel] FreeDOS 1.2

2015-11-20 Thread Mateusz Viste
Hi Geraldo,

Looks nice! Let me know when it is confirmed that translations are okay, 
I will gladly add them. Or, if you wish, I can provide you svn access to 
the project so you can maintain these languages yourself.

Side note: in any case, if/when you provide any files to the 
freedoslocal project (be it through mail or svn), please make sure the 
files are encoded in UTF-8.

cheers,
Mateusz



On 21/11/2015 03:33, Geraldo Netto wrote:
> Hi All,
>
> Based on Rugxulo/Mateusz FreeDOS local link
> I took a few minutes to make some (brazilian) portuguese translations
> of the following softwares:
> (Translatations available at [1])
>
> choice
> compute
> find
> help
> more
> password
> pause
> sort
> tee
> trch
>
> Before asking to push on SVN, i'd like to ask any brazilian or
> portuguese to test and report
> [1] https://www.dropbox.com/sh/agz9n342trjorqg/AAAX8ExU4G0eBwOOgOz_v7Paa?dl=0
>
>
>
> Kind Regards,
>
> Geraldo Netto
> Sapere Aude => Non dvcor, dvco
> http://exdev.sf.net/
>
> On 20 November 2015 at 22:50, Rugxulo  wrote:
>> Hi,
>>
>> On Fri, Nov 20, 2015 at 6:40 PM, Eric Auer  wrote:
>>>
>>> But back to the original question: The installer should
>>> support English, plus any language for which somebody on
>>> this list is interested in giving you a translation of a
>>> message file of your installer :-) For example Spanish,
>>> maybe Portuguese, Russian, French, German, even Dutch ;-)
>>
>> For example, support on http://freedoslocal.sourceforge.net/ is
>> underwhelming, to say the least. As much as some of us would like to
>> fully support at least "some" extra language options, it's just not
>> feasible (without a lot of time and energy, which even enthusiasts
>> like me are lacking these days).
>>
>> So (obviously) it comes down to whoever is willing to do the work. If
>> no one is willing to step up to the plate, then "English only" it is.
>> Not ideal but perhaps unavoidable. (Maybe all such worrying about this
>> should wait until FD 1.2.1 or 1.3 or 2.0.)
>>
>> --
>> ___
>> Freedos-devel mailing list
>> Freedos-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
> --
>



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


Re: [Freedos-devel] FreeDOS 1.2

2015-11-20 Thread Geraldo Netto
Hi All,

Based on Rugxulo/Mateusz FreeDOS local link
I took a few minutes to make some (brazilian) portuguese translations
of the following softwares:
(Translatations available at [1])

choice
compute
find
help
more
password
pause
sort
tee
trch

Before asking to push on SVN, i'd like to ask any brazilian or
portuguese to test and report
[1] https://www.dropbox.com/sh/agz9n342trjorqg/AAAX8ExU4G0eBwOOgOz_v7Paa?dl=0



Kind Regards,

Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/

On 20 November 2015 at 22:50, Rugxulo  wrote:
> Hi,
>
> On Fri, Nov 20, 2015 at 6:40 PM, Eric Auer  wrote:
>>
>> But back to the original question: The installer should
>> support English, plus any language for which somebody on
>> this list is interested in giving you a translation of a
>> message file of your installer :-) For example Spanish,
>> maybe Portuguese, Russian, French, German, even Dutch ;-)
>
> For example, support on http://freedoslocal.sourceforge.net/ is
> underwhelming, to say the least. As much as some of us would like to
> fully support at least "some" extra language options, it's just not
> feasible (without a lot of time and energy, which even enthusiasts
> like me are lacking these days).
>
> So (obviously) it comes down to whoever is willing to do the work. If
> no one is willing to step up to the plate, then "English only" it is.
> Not ideal but perhaps unavoidable. (Maybe all such worrying about this
> should wait until FD 1.2.1 or 1.3 or 2.0.)
>
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel

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


Re: [Freedos-devel] FreeDOS 1.2

2015-11-20 Thread Rugxulo
Hi,

On Fri, Nov 20, 2015 at 6:40 PM, Eric Auer  wrote:
>
> But back to the original question: The installer should
> support English, plus any language for which somebody on
> this list is interested in giving you a translation of a
> message file of your installer :-) For example Spanish,
> maybe Portuguese, Russian, French, German, even Dutch ;-)

For example, support on http://freedoslocal.sourceforge.net/ is
underwhelming, to say the least. As much as some of us would like to
fully support at least "some" extra language options, it's just not
feasible (without a lot of time and energy, which even enthusiasts
like me are lacking these days).

So (obviously) it comes down to whoever is willing to do the work. If
no one is willing to step up to the plate, then "English only" it is.
Not ideal but perhaps unavoidable. (Maybe all such worrying about this
should wait until FD 1.2.1 or 1.3 or 2.0.)

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


Re: [Freedos-devel] FreeDOS 1.2

2015-11-20 Thread Eric Auer

Hi! Let me take your question as an excuse to talk a
bit about support of non-English languages in any DOS,
maybe some of our experts can add interesting comments
and hints about the status of support in FreeDOS :-)

Of course I also answer the original two questions, a
bit further below ;-)

>   What languages would you like to see FDI 1.2 support:
> 
>   English (EN)
>   Spanish (ES)

Installer: English and maybe other popular languages. According to

https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers

you would want to put, in that order: Mandarin Chinese,
Spanish, English, Hindi, Arabic, Portuguese, Bengali,
Russian, Japanese, Punjabi, German... And according to

https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers

you would want to put Mandarin Chinese, English, Spanish,
Hindi, Russian, Portuguese, Bengali, French, Urdu and
Japanese.

As almost nothing in DOS supports Unicode, you will be
out of luck with "wide" Mandarin support. For Hindi,
we would need some ISCII Devangari font, might exist,
but there seem to be combining diacritics which again
is something which has very bad support in DOS apps:

https://en.wikipedia.org/wiki/ISCII

After English and Spanish, support for Russian is the
next most popular *feasible* language. We have suitable
fonts and there are native speakers reading this list,
who could help with translations. Next would be Roman
languages: Portuguese (including Brazilian) and French.
Finally Urdu and Japanese. Urdu is written right to left
and has rather calligraphic fonts, again bad DOS support
and the same for Devangari font. HOWEVER, it is possible
to write Urdu in "normal" (ASCII and accents) codepages:

https://en.wikipedia.org/wiki/Roman_Urdu

Similarily, you CAN write Japanese in Katakana, for which
a DOS-friendly half-width variant exists, or even Romaji,
which is basically ASCII...

https://en.wikipedia.org/wiki/Half-width_kana

For Chinese, you could use Pinyin, which is the romanized
"spelling out" of Mandarin for situations where only ASCII
is supported, either for display or simply because a QWERTY
keyboard is used to type, with "input method" support then
turning the typed text into the proper Unicode characters.

*end of very international ponderings*

But back to the original question: The installer should
support English, plus any language for which somebody on
this list is interested in giving you a translation of a
message file of your installer :-) For example Spanish,
maybe Portuguese, Russian, French, German, even Dutch ;-)

For the installed software itself, you simply enjoy what
the individual packages already have, translation-wise.

Note that for FreeCOM command.com you need some special
install steps: Basically you copy together a stub and a
message file to make a command.com in 1 of the languages
for which we have translations. Similarily, CuteMouse is
available in various pre-compiled (translated) variants.

Basically all other tools work with the LANG and NLSPATH
settings, so you always install them the normal way and
they switch to other languages simply based on LANG :-)

This also means that if you see a package in FreeDOS which
uses LANG but has no translation in a popular language, it
is possible to ask for a translation on this list and add
the new translation to the package in the repository :-)

You can also let us know if there is a package for which
translations would be sort of important but for which no
mechanism of translation is available at all. Note that
for various small and simple tools, language support is
seen as unnecessary and too heavy on the disk space side,
as it would mean having to add advanced string processing.

*And finally*

> Second:
> 
>   Nobody has any idea on what additional packages are
>   to be included in “all packages”?

As there is a lot of space on a CD or even DVD, "all" would
mean the full packages (including sources) for everything on
http://www.freedos.org/software/ which is probably very much
the same as "everything in Mateusz' FDNPKG package repository
server". You probably want to check that and check for which
packages the homepage of the project in question has "fresh"
versions not yet available in Mateusz' repository. Once you
know which those are, you can help him to update the server,
or post the list on this list to find others to help updating.

Cheers, Eric



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


[Freedos-devel] FreeDOS 1.2

2015-11-20 Thread Jerome E. Shidel Jr.
First:

What languages would you like to see FDI 1.2 support:

English (EN)
Spanish (ES)

(anything else?)

Second:

Nobody has any idea on what additional packages are
to be included in “all packages”?
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] picoTCP: a modern, open-source TCP/IP stack for DOS

2015-11-20 Thread Mercury Thirteen
Many thanks for this! Wonderful work.

On 11/19/2015 2:00 PM, Mateusz Viste wrote:
> Hello group,
>
> I write this message to share a little news about what I was doing in my
> spare time these last two months: porting picoTCP to DOS.
>
> picoTCP is a modern, dual-stack, open-source TCP/IP stack. It has been
> created by the good people at Intelligent Systems (Altran), primarily as
> a stack designed for embedded computing (hence hardware with very
> limited horse power). It is backed by a well established corporation and
> it's actively maintained.
>
> I played with the stack for some times now, and ended up building an
> entire DOS compatibility layer around it. A few patches were required to
> the stack, a few days of development, many hours of debugging - but here
> it is - the first public release of picoTCP for DOS!
>
> http://picotcp4dos.sourceforge.net
>
> The project contains three major parts:
>
> - ipcfg: a little tool that allows to configure networking on your DOS
> machine (IP, DNS, etc). No, it's not a text file - I wanted to avoid the
> complexity of parsing a text file, and opted for a binary configuration
> file that is manipulated via ipcfg. It's much more flexible that a text
> config file, while being much easier/faster to load at runtime.
>
> - ping: no need to explain, I guess... my ping tool for DOS, based on
> picoTCP - crucial when it comes to testing your networking
>
> - an OpenWatcom library package (openwatcom, large memory model) - this
> is for the fellow developers that would like to use the DOS version of
> picoTCP inside their network-enabled, 16-bit DOS programs. I integrated
> a packet driver schim, a DOS-compatible timer, as well as the whole IP
> configuration logic, so it is now a simple (2 functions!) public API
> that allows to load picoTCP, use it, and unload it.
>
>
> *** Short how-to ***
>
> 1. Download picotcp4dos and unzip it on your drive
> 2. Set the location where the config file will be stored, for example:
> SET PICOTCP=C:\PICOTCP.DAT
> 3. Bind picoTCP to the interrupt vector of your packet driver, example:
> ipcfg int 60
> 4. Configure your IP settings using ipcfg, or use DHCP (ipcfg dhcp)
>
> enjoy!
>
> Mateusz
>
>
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


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