 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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:
>>
>> ..../distribution/scenes/objects/superel2.pov
>>
>> 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. :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
William F Pokorny <ano### [at] anonymous org> wrote:
> 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:
> >>
> >> ..../distribution/scenes/objects/superel2.pov
> >>
> >> 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?
At the very least, it seems logical to increment the line count. I don't think
it would be necessary--or, at this late date, prudent--to assume a certain
number of lines per page.
[...]
> (1) - Do I admit my earliest college programming classes used teletype
> computer terminals... Ah, the noise. :-)
You make me feel young, now. I had VT-100s in college.
Although at my co-op job, I actually had to deal with punched cards and IBM's
JCL.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/15/19 8:21 AM, Cousin Ricky wrote:
> William F Pokorny <ano### [at] anonymousorg> wrote:
>
> At the very least, it seems logical to increment the line count. I don't think
> it would be necessary--or, at this late date, prudent--to assume a certain
> number of lines per page.
Not sure. The common unix line counting command shows the line count
(and character) as if the form feed and vertical tab characters are just
spaces.
Editors seem to be different. GVim (1) is showing ^L and ^K stand in
sequences and then columns after in each line as a range, 10-11 say,
instead of a fixed 10. Gedit shows single undefined unicode characters
breaking the mono-space width. Others tried create a mono-space stand at
least indicating some odd character is present and the visual
representation stays aligned. Expect some of the editor behavior is
driven by the font in use. Though in trying a few different fonts with
gvim, fixed and not, it is always showing the ^L or ^K sequence and some
visual miss-alignment.
(1) - all vi based editors I expect
>
> [...]
>
>> (1) - Do I admit my earliest college programming classes used teletype
>> computer terminals... Ah, the noise. :-)
>
> You make me feel young, now. I had VT-100s in college.
>
> Although at my co-op job, I actually had to deal with punched cards and IBM's
> JCL.
>
>
JCL :-). How do we want the file xyz to physically exist on the drive...
I worked with it a fair bit early in my work career.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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:
>>>
>>> ..../distribution/scenes/objects/superel2.pov
>>>
>>> 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
|
|
| |
| |
|
|
|
|
| |
|
|
