 | | Re: Backwards Compatibility (Was Calling all Meta-commands) —Dan Boger
|
| | | (...) Exactly because it's not likely to be used, ever, by mistake. Anyone can put whatever comments they like in a dat, right? So if I write a dat, and want to enter 0 METAL RAIL STARTS HERE and typo it into 0 META LRAIL STARTS HERE (which is a (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| | | |
| | | | | Re: Backwards Compatibility (Was Calling all Meta-commands) —Tim Courtney
|
| | | | | (...) Points taken :-) And ultimately, I'm not going to be involved in making the decision, since I won't be volunteering for the standards body [1]. Just getting in my .02 here while I can ;-) -Tim [1] I don't have the knowledge to discuss some (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| | | | | |
| | | | | Re: Backwards Compatibility (Was Calling all Meta-commands) —Tore Eriksson
|
| | | | (...) I don't know about American keyboards, but at my Swedish kb, '{' and '}' are at AltGr+7 and AltGr+0, and it collides with Swedish special characters in the ASCII table; it has to be set on codepage 850 or whatever it was. I find them somewhat (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Backwards Compatibility (Was Calling all Meta-commands) —Tore Eriksson
|
| | | | (...) What I mean is: (URL) for example. Quite corrupted and hard to read - even for us who understand Swedish. ;-) I don't know whether brackets will be cause the same kind of problems, but there is a risk. Then a line from a posted part or model (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Backwards Compatibility (Was Calling all Meta-commands) —Fredrik Glöckner
|
| | | | (...) This problem is not due to the Swedish character set, but rather a problem with the Lugnet web interface. The Lugnet web interface does not support RFC2047 encoded header fields, that explains the problems with the subject line. I have (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| | | | |
