I AM using The Times New Roman font.
Getting Windows-XP would indeed be the Endloesung for me, as it does
not run the DOS32 programs which I write (in Modula-2).
Who says DOS programs don't run under XP? All of mine do! The only DOS
applications I've found that don't run under XP are those that do unusual
input/output (e.g., addressing ports directly). And even then, the common
operations (e.g., on the serial port) still work. Send me one of the
executables and I'll try it under XP if you'd like.
In the log run I will be forced to learn Windows programming and I am
NOT looking forward towards it, as it is much more complex than good
old DOS and does not add much as far as I can see - my programs are
all purely text oriented.
That complexity is a thing of the past. I, too, refused to learn "Windows
programming" in raw C the way it was done in the early 1990s, where you had
to write 2 pages of code just to say "hello, world" in a window. Nowadays
you have a lot of options:
- Keep using DOS compilers. (I still use Turbo Pascal 3 for quick
calculations.)
- Write "console mode" (non-windowed) programs in C or whatever you like.
You do not have to do anything special for Windows; many simple C programs
port directly from UNIX unaltered. The program runs in a "console window"
and uses the screen and keyboard just as if it were running on a computer of
the 1970s. They still have the full memory and speed of the Windows XP
system, and they can call any Windows system routine.
- Use Delphi. This is windowed programming made easy, in a language
directly descended from Turbo Pascal. You can also write console mode
programs.
- (The best) Use C#. This is the latest descendant of Pascal and Modula,
although the syntax looks like C. It was designed by the man who gave us
Turbo Pascal and Delphi (Anders Hejlsberg). Both console mode and windowing
are very convenient. And the spirit of it is structured and object-oriented
programming (a la Pascal and Modula-2) rather than low-level tricks (a la C
and C++). Only the syntax looks like C; it's C with a Pascal brain.
As a temporary solution I replace the sheva/pepet signs with an /e/
with an v-shaped diacritical mark on top (an upside-down circonflex as
it were) (Unicode 283 instead of Unicode 277). This character is
visible on screen and will also print.
Of course, we should actually *solve* your problem, instead of just
*guessing* that Windows XP will solve it. One thing's for sure -- Windows
98 is not going to be updated any more, so if you stick with 98, things will
never change. Can anyone shed any light on why this particular Unicode
character won't print? Have you tried a different printer driver?
--
Michael A. Covington - Artificial Intelligence Ctr - University of Georgia
"In the core C# language it is simply not possible to have an uninitialized
variable, a 'dangling' pointer, or an expression that indexes an array
beyond its bounds. Whole categories of bugs that routinely plague C and C++
programs are thus eliminated." - A. Hejlsberg, The C# Programming Language
