Re: [NTG-pdftex] 1.40.4 incoming
Uh, isn't EOF operating-system dependent? Like C-z on Microsoft Systems?
I'll apply the following ctrld-ctrlz.ch for Windows:
@x print_ln; print("(Retry if file name is empty or CTRL-D to exit."); @y print_ln; print("(Retry if file name is empty or CTRL-Z + Enter to exit."); @z
In this case, we may not be able to use the common pool files. Is EOF by Philip Taylor better? Best regards, Akira
On Tue, Jul 10, 2007 at 09:57:18AM +0900, Akira Kakuto wrote:
Uh, isn't EOF operating-system dependent? Like C-z on Microsoft Systems?
I'll apply the following ctrld-ctrlz.ch for Windows:
@x print_ln; print("(Retry if file name is empty or CTRL-D to exit."); @y print_ln; print("(Retry if file name is empty or CTRL-Z + Enter to exit."); @z
In this case, we may not be able to use the common pool files.
A dummy string might be inserted so that the pool file contains both string variants.
Is EOF by Philip Taylor better?
I doubt that many users will know which keys to press.
Yours sincerely
Heiko
Heiko Oberdiek wrote:
On Tue, Jul 10, 2007 at 09:57:18AM +0900, Akira Kakuto wrote:
Uh, isn't EOF operating-system dependent? Like C-z on Microsoft Systems? I'll apply the following ctrld-ctrlz.ch for Windows:
@x print_ln; print("(Retry if file name is empty or CTRL-D to exit."); @y print_ln; print("(Retry if file name is empty or CTRL-Z + Enter to exit."); @z In this case, we may not be able to use the common pool files.
A dummy string might be inserted so that the pool file contains both string variants.
I vote for Phil's approach. I suspect most of the people that do not know how to generate an EOF in the console will not understand the key press reference either. Besides, tricks like dummy strings tend to lead to bugs in the years to come. (said as the person who just spend a whole day figuring out that the weird "file_name_size=maxint" statement in tex.ch is part of a trick to simplify openclose.c as it forces the "namelength" var to be of the correct allocation size). Best wishes, Taco
2007/7/10, Taco Hoekwater
I vote for Phil's approach. I suspect most of the people that do not know how to generate an EOF in the console will not understand the key press reference either.
Besides, tricks like dummy strings tend to lead to bugs in the years to come. (said as the person who just spend a whole day figuring out that the weird "file_name_size=maxint" statement in tex.ch is part of a trick to simplify openclose.c as it forces the "namelength" var to be of the correct allocation size).
Agreed. KISS :-) Best Martin
On Tue, Jul 10, 2007 at 08:42:57AM +0200, Taco Hoekwater wrote:
Heiko Oberdiek wrote:
On Tue, Jul 10, 2007 at 09:57:18AM +0900, Akira Kakuto wrote:
Uh, isn't EOF operating-system dependent? Like C-z on Microsoft Systems? I'll apply the following ctrld-ctrlz.ch for Windows:
@x print_ln; print("(Retry if file name is empty or CTRL-D to exit."); @y print_ln; print("(Retry if file name is empty or CTRL-Z + Enter to exit."); @z In this case, we may not be able to use the common pool files.
A dummy string might be inserted so that the pool file contains both string variants.
I vote for Phil's approach. I suspect most of the people that do not know how to generate an EOF in the console will not understand the key press reference either.
Yes, there are people who don't understand "CTRL" or "Enter", but I wouldn't want to recommend TeX for them.
Besides, tricks like dummy strings tend to lead to bugs in the years to come. (said as the person who just spend a whole day figuring out that the weird "file_name_size=maxint" statement in tex.ch is part of a trick to simplify openclose.c as it forces the "namelength" var to be of the correct allocation size).
The solution is simple, just make the string more informative.
Example:
Leave the file name empty to re-try,
or enter <eof> (Unix: CTRL-D, Windows: CTRL-Z + Enter) to exit.
Yours sincerely
Heiko
On 7/10/07, Heiko Oberdiek
The solution is simple, just make the string more informative. Example: Leave the file name empty to re-try, or enter <eof> (Unix: CTRL-D, Windows: CTRL-Z + Enter) to exit.
Then you have to explain that linux uses unix <eof> -- maybe
"Leave the file name empty to re-try, or type the end-of-file code for
your platform to exit."
Goggle for "windows end-of-file" got a bunch of hits that mention
using <Ctrl-Z>.
Goggle for "linux end-of-file" got a bunch of hits that mention using <Ctrl-D>.
Goggle for "unix end-of-file" got a a few of hits that mention using <Ctrl-D>
Goggle for "OS X end-of-file" doesn't appear to be helpful!
--
George N. White III
My point was more that it should be phrased as an instruction rather than an observation, e.g., "Press ... to ..., or ... to ..." or "Enter ... to ..., or ... to ..." ** Phil. -------- Heiko Oberdiek wrote:
On Tue, Jul 10, 2007 at 09:57:18AM +0900, Akira Kakuto wrote:
Is EOF by Philip Taylor better?
I doubt that many users will know which keys to press.
Yours sincerely Heiko
2007/7/10, Heiko Oberdiek
On Tue, Jul 10, 2007 at 09:57:18AM +0900, Akira Kakuto wrote:
In this case, we may not be able to use the common pool files.
A dummy string might be inserted so that the pool file contains both string variants.
Patch? Best Martin
participants (6)
-
Akira Kakuto -
George N. White III -
Heiko Oberdiek -
Martin Schröder -
Philip TAYLOR -
Taco Hoekwater