Now that we have "allow8bit 1" as an option in our modern MakeNl
configs, how many of you chose not to use it? I.e. not to allow
characters above the old ASCII seven bit restriction.
It would be interesting to know where the eight bit option is held back,
because obviously it still is, despite the developer's attempt to
remove that archaic restriction.
Now that we have "allow8bit 1" as an option in our modern MakeNl configs, how many of you chose not to use it? I.e. not to allow characters above the old ASCII seven bit restriction.
It would be interesting to know where the eight bit option is held back, because obviously it still is, despite the developer's attempt to remove that archaic restriction.
Zone wise, region wise, net wise, hub wise, whatever.
Do you seriously believe that people would start using your local
UTF nodelist, not supported by any known nodelist to mailer compiler,
Do you seriously believe that people would start using your local UTF nodelist, not supported by any known nodelist to mailer compiler, just to get what we already can get with the present global setup?
You really are in dire need of a big chunk of FTN reality check, Michiel.
And now, finally, all it takes is for Ward to
add that elusive "allow8bit 1" to his MakeNl config -- but somehow he
still refuses to do that.
But my question was most of all directed at all the *Cs not involved
with the R28/R29 war going on.
Once upon a time, up in the northernmost part of Europe, there was a constant struggle about what codepage to use. We had PC, Amiga and Mac owners who all pushed for their hardware installed code page.
Eventually we got CP850, and it was the perfect compromise. It had all the characters normally used in Swedish, and most other west European languages, in place. And later on, when Windows came into play, their Amiga-ish encoding also fit perfectly well.
So, what code page do you think would be best?
That has to wait until we decide what codepage is to be used.
So there's a R28/R29 war going on?
If so it must be the most boring war ever because I'm not aware, neither is RC28 nor RC29 ... Please enlighten us ...
Feel free to answer this simple question:
Why did you suddenly increase the number of regions, when so many of
us (e.g. R20, R21, R22 and R23 merging into the single R20) did our best
to reduce it?
So, what code page do you think would be best?
Your solutions apparently fits the Scandinavian country,
"Ah well, CP 850 is the primary code page and default OEM code page in many countries, including various English-speaking locales (e.g. in the United Kingdom, Ireland, and Canada)."
Are you saying that your country is not included?
Or that it does not include almost all countries in the western
world?
Yes, I know that it can't handle Cyrillic, Arabic, Chinese, Korean, Japanese and a lot of other languages, but will you claim that it does not cover the vast majority of countries actively taking part of the international Fidonet?
Your solutions apparently fits the Scandinavian country, but that is
not the majority of Fidonet. The encoding of the of the Nodelist is a matter of the whole of Fidonet.
For the Whole of Fidonet the least common denominator is still 7bit ascii. The other side of the spectrum is UTF-8.
But fidonet is not tuned to multi- byte characters.
From the outside
it sure looks like a civil war, where some were seeking independence from the 15yo union. Why? Please enlighten us...
From the outside
it sure looks like a civil war, where some were seeking independence from
the 15yo union. Why? Please enlighten us...
If you don't have a verifiable clue then keeping quiet is a virtue.
If your favorite code page is so well fitting, why is it not mandatoryin
English speaking Fidonet?
If your favorite code page is so well fitting, why is it not
mandatory in
English speaking Fidonet?
Who would make it, and how? And why? The code page is all about presentation. Fidonet is a network. As such it does not care shit what data it transports. Net neutrality has always been important for Fidonet, the network.
I know that Fidonet is usually confused with the mail that it transports. Exactly like Internet is confused with the WWW.
Now it's too late to teach everyone the difference and how the OSI layer works, because nobody cares any more. All that they, save for a few remaining hardcore techies, care about is how what they receive is presented.
That is peanuts to what the sysops in the eastern countries have toenjure.
I know, and as the responsible RC I try to be, I've been trying to
play for many years now.
And now, finally, all it takes is for Ward to add that elusive
"allow8bit 1" to his MakeNl config -- but somehow he still refuses to
do that.
And I sense that you have something to do with that with your
beloved UTC nodelist that nobody needs.
But my question was most of all directed at all the *Cs not
involved with the R28/R29 war going on.
If my 2:203/208 is flagged ;E we know if you speak the truth.
http://nodehist.fidonet.org.ua/?address=2%3A203%2F6
Once again many thanks to Pavel Gulchouck 2:463/68
Are you saying that your country is not included?
Or that it does not include almost all countries in the western world?
Yes, I know that it can't handle Cyrillic, Arabic, Chinese, Korean, Japanese and a lot of other languages,
but will you claim that it does not cover the vast majority of
countries actively taking part of the international Fidonet?
And you know this for a fact?
How?
To me he told me that he never heard about it before I brought it to
his attention. Once again.
Alas, we'll see in the next nodelist where I once again am trying
it, after having tried it for three years with my 2:203/6 entry:
Here we go again. Who made you the spokesperson for the Russians?
| Sysop: | Zazz |
|---|---|
| Location: | Mesquite, Tx |
| Users: | 7 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 61:31:44 |
| Calls: | 157 |
| Files: | 2,109 |
| Messages: | 145,291 |