| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 972.1 | | ZFC::DERAMO | Daniel V. {AITG,ZFC}:: D'Eramo | Wed Nov 09 1988 20:41 | 13 |
| One problem with character cell graphics -- the DECwindows
version of NOTES apparently uses a variable width font; at
any rate the individual lines of multi-line formulas such
as:
2 2 2
x + y = z
no longer lined up, so what I saw looked more like:
2 2 2
x + y = z
Dan
|
| 972.2 | Sixels would be better. | DWOVAX::YOUNG | Note early. Note Often. | Thu Nov 10 1988 01:58 | 14 |
| Sixels would be much better for me than PostScript.
At the moment, and for the forseeable future, I am not going to
have any way to access an interactive display PostScript device.
I do have access to a PostScript printer at the office, but I get
in to the office only about once a month (life in the field has
its drawbacks).
On the other hand, all of the terminals that I use to access the
Enet with DO have Sixel capabilities. I realize that PostScript
has many toher advantages over Sixels, and that it is the way of
the future, but these two points are real show-stoppers for me.
-- Barry
|
| 972.3 | Anybody got a postscript-to-sixel converter? | POOL::HALLYB | The smart money was on Goliath | Thu Nov 10 1988 15:15 | 1 |
|
|
| 972.4 | | AITG::DERAMO | Daniel V. {AITG,ZFC}:: D'Eramo | Thu Nov 10 1988 16:20 | 9 |
| re: Anybody got a postscript-to-sixel converter?
My workstation has DECwindows, so I should be able to view
postscript files in a window, and capture that using the
"print portion of screen" feature into a sixel file or a
DDIF file (or a postscript file, but that's what it started
as).
Dan
|
| 972.5 | Edit postscript files before viewing! | CDROM::JAGGER | | Tue Nov 15 1988 21:09 | 16 |
|
> re: Anybody got a postscript-to-sixel converter?
> My workstation has DECwindows, so I should be able to view
> postscript files in a window, and capture that using the
> "print portion of screen" feature into a sixel file or a
> DDIF file (or a postscript file, but that's what it started
> as).
Not only that, but you can edit the postscript file and add scale, and
translation commands, so that text is readable as a sixel file. We are
currently taking postscript files and generating sixel files from this
very process!
TOM
|
| 972.6 | DDIF for pictures | CLT::GILBERT | Multiple inheritence happens | Tue Nov 22 1988 17:20 | 11 |
| And the answer is ... DDIF.
The DECwindows version of VAX Notes (T2.0-10) supports DDIF notes.
When you write the note, use the 'use existing file...' option in the
'File' pull-down menu. Sorry, VAX Notes doesn't let you edit/compose
the DDIF note, you'll have to use EPIC/write for that. VAX Notes
*does* display the DDIF note using the DDIF viewer, and will convert
DDIF notes to simple text if appropriate/possible (just as RMS does
if you type or compile a DDIF file).
BTW, DECwindows Mail also supports DDIF files.
|
| 972.7 | How thick are the lines :-) ? | AKQJ10::YARBROUGH | I prefer Pi | Tue Nov 22 1988 18:17 | 5 |
| An important factor here is file size, since notes become sorta permanent.
Can someone tell me the relative volume of DDIF vs PostScript files for a
line drawing?
Lynn Yarbrough
|
| 972.8 | | AITG::DERAMO | Daniel V. {AITG,ZFC}:: D'Eramo | Tue Nov 22 1988 21:15 | 5 |
| It might be best to post a pointer to a world-readable file
on your own machine. With a simple "ascii diagram" in the
note for those who don't have DECwindows workstations.
Dan
|
| 972.9 | one problem (from .1) has been fixed | AITG::DERAMO | Daniel V. {AITG,ZFC}:: D'Eramo | Fri Mar 03 1989 19:19 | 25 |
| re .1
>> One problem with character cell graphics -- the DECwindows
>> version of NOTES apparently uses a variable width font; at
>> any rate the individual lines of multi-line formulas such
>> as:
>> 2 2 2
>> x + y = z
>>
>> no longer lined up, so what I saw looked more like:
>>
>> 2 2 2
>> x + y = z
This is from the notes release notes, note 3.3 of CLT::VAXNOTES_V20_IFT
dated 18-JAN-1989.
>> o The Read window formerly did not display <TAB> characters in
>> the text of the note. This problem has been fixed.
I haven't noticed the problem I mentioned in .1 for a long time.
Apparently it wasn't a variable width font, it was tab characters
not being handled correctly. That's fixed now.
Dan
|