On Fri, 3 Nov 2006, Ales Katona wrote:
>
> > I am already adding lnet and synapse support to fppkg.
> > (to WST too, BTW ;) ) The wget is a fallback and proof
> > of concept implementation.
>
> I've got a skeleton lNet/fppkg done localy now, will finish it tomorrow
> (and hopefuly find a wa
> I am already adding lnet and synapse support to fppkg.
> (to WST too, BTW ;) ) The wget is a fallback and proof
> of concept implementation.
I've got a skeleton lNet/fppkg done localy now, will finish it tomorrow
(and hopefuly find a way to test :) )
I've put lNet to fcl for local setup too
Op Fri, 3 Nov 2006, schreef Tomas Hajny:
> > Xterm supports two modes: ISO-8859-1 and UTF-8. There are two ways to use
> > a different code page:
> > * Put the xterm in ISO-8859-1 mode and just load a font with different
> > characters in #128..#255.
> > * Use proper fonts, but use an emulator
On Fri, 3 Nov 2006, Ales Katona wrote:
> I've noticed Michael just added a "wget" package getter to the new
> packager.
Yes.
>
> We already had a small discussion about using lNet in the new packaging
> system and it comes down to this:
>
> The packager needs pure fpc solution, which lNet no
I've noticed Michael just added a "wget" package getter to the new
packager.
We already had a small discussion about using lNet in the new packaging
system and it comes down to this:
The packager needs pure fpc solution, which lNet now is, but won't be
later (eg: when openSSL is added)
I'm willi
On 11/3/06, Tomas Hajny <[EMAIL PROTECTED]> wrote:
ik wrote:
> On 11/3/06, Micha Nelissen <[EMAIL PROTECTED]> wrote:
>> Tomas Hajny wrote:
>> > Does anybody here have an idea how to address that issue in Unix/Linux
>> > environment (like an environment variable similar to TERM, etc.)? I
>> can
>>
ik wrote:
> On 11/3/06, Micha Nelissen <[EMAIL PROTECTED]> wrote:
>> Tomas Hajny wrote:
>> > Does anybody here have an idea how to address that issue in Unix/Linux
>> > environment (like an environment variable similar to TERM, etc.)? I
>> can
>>
>> The part after the dot in $LANG. It's possible th
Micha Nelissen napsal(a):
> ik wrote:
>>> The part after the dot in $LANG. It's possible though that there is no
>>> dot, no idea what to do, maybe assume iso-8859-1 ?
>>
>> No, that will be really bad idea to assume iso-8859-1 . It really
>> depends on the country and language code. For example :
Daniël Mantione wrote:
> Op Fri, 3 Nov 2006, schreef Tomas Hajny:
>
>> This is something to be addressed in video.pp - we need to detect the
>> character set supported by console at startup (optionally with a
>> possibility to change it later on). This is something we partly touched
>> in
>> discus
Marco van de Voort schrieb:
Marco van de Voort schrieb:
Tomas Hajny wrote:
Does anybody here have an idea how to address that issue in Unix/Linux
environment (like an environment variable similar to TERM, etc.)? I can
The part after the dot in $LANG. It's possible though that there is no
dot,
Op Fri, 3 Nov 2006, schreef Marco van de Voort:
> > Op Fri, 3 Nov 2006, schreef Marco van de Voort:
> >
> > > While ok in general, some older systems might still be in whatever the
> > > vgafont specifies (iow dos CP437) on the console.
> >
> > The Linux console always boots up in Latin-1 mode
> Op Fri, 3 Nov 2006, schreef Marco van de Voort:
>
> > While ok in general, some older systems might still be in whatever the
> > vgafont specifies (iow dos CP437) on the console.
>
> The Linux console always boots up in Latin-1 mode, with a code page
> 437 loaded into the VGA. The console is a
Op Fri, 3 Nov 2006, schreef Marco van de Voort:
> While ok in general, some older systems might still be in whatever the
> vgafont specifies (iow dos CP437) on the console.
The Linux console always boots up in Latin-1 mode, with a code page
437 loaded into the VGA. The console is another matte
> Marco van de Voort schrieb:
> >> Tomas Hajny wrote:
> >>> Does anybody here have an idea how to address that issue in Unix/Linux
> >>> environment (like an environment variable similar to TERM, etc.)? I can
> >> The part after the dot in $LANG. It's possible though that there is no
> >> dot, no i
> Marco van de Voort wrote:
> >> The part after the dot in $LANG. It's possible though that there is no
> >> dot, no idea what to do, maybe assume iso-8859-1 ?
> >
> > It is also possible there is no LANG, like on all four Stack systems I
> > quickchecked. (freebsd,Solaris and debian mixed)
>
> N
Op Fri, 3 Nov 2006, schreef Micha Nelissen:
> Marco van de Voort wrote:
> >> The part after the dot in $LANG. It's possible though that there is no
> >> dot, no idea what to do, maybe assume iso-8859-1 ?
> >
> > It is also possible there is no LANG, like on all four Stack systems I
> > quickche
Marco van de Voort wrote:
>> The part after the dot in $LANG. It's possible though that there is no
>> dot, no idea what to do, maybe assume iso-8859-1 ?
>
> It is also possible there is no LANG, like on all four Stack systems I
> quickchecked. (freebsd,Solaris and debian mixed)
No language => as
Marco van de Voort schrieb:
Tomas Hajny wrote:
Does anybody here have an idea how to address that issue in Unix/Linux
environment (like an environment variable similar to TERM, etc.)? I can
The part after the dot in $LANG. It's possible though that there is no
dot, no idea what to do, maybe ass
> Tomas Hajny wrote:
> > Does anybody here have an idea how to address that issue in Unix/Linux
> > environment (like an environment variable similar to TERM, etc.)? I can
>
> The part after the dot in $LANG. It's possible though that there is no
> dot, no idea what to do, maybe assume iso-8859-1
Op Fri, 3 Nov 2006, schreef Tomas Hajny:
> This is something to be addressed in video.pp - we need to detect the
> character set supported by console at startup (optionally with a
> possibility to change it later on). This is something we partly touched in
> discussion with Daniel in Eindhoven (
ik wrote:
>> The part after the dot in $LANG. It's possible though that there is no
>> dot, no idea what to do, maybe assume iso-8859-1 ?
>
> No, that will be really bad idea to assume iso-8859-1 . It really
> depends on the country and language code. For example :
It doesn't depend on the langua
On 11/3/06, Micha Nelissen <[EMAIL PROTECTED]> wrote:
Tomas Hajny wrote:
> Does anybody here have an idea how to address that issue in Unix/Linux
> environment (like an environment variable similar to TERM, etc.)? I can
The part after the dot in $LANG. It's possible though that there is no
dot,
On 11/3/06, Tomas Hajny <[EMAIL PROTECTED]> wrote:
Marco van de Voort wrote:
>> On Thu, 2 Nov 2006, Matthew V. Kotov wrote:
>>
>> > Hello,Free Pascal development team!
>> >
>> > Sorry, I speak English very bad.
>> >
>> > In file fpcsrc/rtl/unix/video.pp nessesary take away lines:
>> >
>> >
Tomas Hajny wrote:
> Does anybody here have an idea how to address that issue in Unix/Linux
> environment (like an environment variable similar to TERM, etc.)? I can
The part after the dot in $LANG. It's possible though that there is no
dot, no idea what to do, maybe assume iso-8859-1 ?
Micha
___
Marco van de Voort wrote:
>> On Thu, 2 Nov 2006, Matthew V. Kotov wrote:
>>
>> > Hello,Free Pascal development team!
>> >
>> > Sorry, I speak English very bad.
>> >
>> > In file fpcsrc/rtl/unix/video.pp nessesary take away lines:
>> >
>> > If fpGetEnv('TERM')='xterm' then
>> >N
> On Thu, 2 Nov 2006, Matthew V. Kotov wrote:
>
> > Hello,Free Pascal development team!
> >
> > Sorry, I speak English very bad.
> >
> > In file fpcsrc/rtl/unix/video.pp nessesary take away lines:
> >
> > If fpGetEnv('TERM')='xterm' then
> >NoExtendedFrame := true; {use o
On Thu, 2 Nov 2006, Matthew V. Kotov wrote:
> Hello,Free Pascal development team!
>
> Sorry, I speak English very bad.
>
> In file fpcsrc/rtl/unix/video.pp nessesary take away lines:
>
> If fpGetEnv('TERM')='xterm' then
>NoExtendedFrame := true; {use of acs for xterm is
Hello,Free Pascal development team!
Sorry, I speak English very bad.
In file fpcsrc/rtl/unix/video.pp nessesary take away lines:
If fpGetEnv('TERM')='xterm' then
NoExtendedFrame := true; {use of acs for xterm is ok}
because it prevents using cyrillic symbols (codepage CP12
From: "Peter Vreman" <[EMAIL PROTECTED]>
The problem is caused by revision 5192 by Peter.
It also adds strange notes like this:
convutil.inc(372,5) Note: Local variable "$hiddenTHEUNITS" not used
This is a known issue and will be solved in time. Don't forget that
Trunk is the development branc
At 11:44 3-11-2006, you wrote:
From: "Gabor Boros" <[EMAIL PROTECTED]>
Subject: [fpc-devel] WinCE compiler compilation is broken
Hi,
The error message is:
math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you
use the correct run time library.
The problem is caused by revision 5192
From: "Gabor Boros" <[EMAIL PROTECTED]>
Subject: [fpc-devel] WinCE compiler compilation is broken
Hi,
The error message is:
math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you use
the correct run time library.
The problem is caused by revision 5192 by Peter.
It also adds strange
SVN 5194
>wich fpc2.1.1 thrunk svn version ?
>last i checked was 5172 from yesterday and was ok
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
wich fpc2.1.1 thrunk svn version ?last i checked was 5172 from yesterday and was ok2006/11/3, Gabor Boros <[EMAIL PROTECTED]>:
Hi,The error message is:math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you use
the correct run time library.Gabor
Hi,
The error message is:
math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you use
the correct run time library.
Gabor
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
34 matches
Mail list logo
