Le 19-01-15 à 06:03, William F Pokorny a écrit :
> On 1/14/19 3:54 PM, clipka wrote:
>> Am 14.01.2019 um 18:23 schrieb William F Pokorny:
>>> One of our standard shipped scene files fails due a form feed
>>> character '0c' very near the end the end of the file. That scene is:
>>> and here I think we just need to update that scene file.
>> Page breaks used to be common in ASCII files a while ago; I feel
>> somehow inclined to just allow them as whitespace.
>> The only thing that's holding me back is that I'm not exactly sure
>> what effect they should have on column and line counting.
> Yeah, suppose they could be as whitespace. Then we'd want to provide the
> same treatment for some other printer(system bell?) oriented encodings
> too if you go that route. Vertical-tab comes to mind & expect there are
> a few more.
> Even in the old days it was printer dependent in terms of real world
> space(1) so not sure treating those special characters as something
> other than a single white space makes sense. I say this, though, not
> knowing what the POV-Ray windows editor does which such characters?
> As for having these kind of characters in sample scene files we ship,
> suppose I'd argue they shouldn't exist. In my editor/font I get some odd
> fill-in character for it. I'm not sure what others might or might not see.
> Bill P.
> (1) - Do I admit my earliest college programming classes used teletype
> computer terminals... Ah, the noise. :-)
Treating form feed as just line feed or new line should be correct.
Post a reply to this message