 | | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) We are talking about official files in the parts library here. They're not going to have Unicode or special characters. If this isn't already explicitly in the spec for library filenames, we can certainly add it. As a side note, UTF-8 and (...) (19 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) Couldn't that be dealt with by restricting the filenames to alphanumerics + the usual suspects (_ etc.)? My understanding was those were unchanged in any character set. Tim (19 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) Call me paranoid, but long filenames make me nervous because of the other worms packaged along with them (like unicode or UTF-8, blech!). Sure your filenames might look great on Windows, but try to bring them over to another filesystem, or (...) (19 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) Or, we should start by introducing the new standard, use it in a few (relatively obscure) instances, and give the various software authors a chance to sort it out. Considering the general pace of parts releases, a long-named file would be on (...) (19 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) This suprises me. Can you elaborate on this? If we in the LSC are going to make an informed decision on this issue, understanding why this is the case with LPub/LSynth would help us greatly. I know all Win32 API calls work fine with long (...) (19 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
