2016-02-18 20:31 GMT+02:00 Dirk Laurie :
> 2016-02-18 17:43 GMT+02:00 Don Simons
>
>> Next, when I run pmx, the pasted umlaut o does get copied
>> into the tex file, but when tex'ing the result, it is not recognized
>> at all; I don't even get a blank space.
>
> 1. Select a font (not Computer Mode
2016-02-18 22:38 GMT+02:00 :
> But first I'll have to refresh my memory about whether
> I can use inline TeX at all inside a lyrics string;
You can, but don't terminate it with a space (that confuses
musixlyr). Put it in braces.
---
TeX-music@tug.org mailing list
If y
When googling 'umlaut qwerty' :
a)
1. turn num Lock on
2. press the Alt-key and the following digits on the numbers pad to the
right:
132 = ä
148 = ö
129 = ü
225 = ß (now defunct)
142 = Ä
153 = Ö
154 = Ü
Add Shift for upper case umlauted characters.
b)
AltGR + s = scharfes S
AltGR + p = o umla
>|if I try to extract parts from the following pmx code
>|(but this happens in many other cases) with scor2prt that
>|comes with pmx273 version I have the following error:
>|
>|*** This is scor2prt for PMX 2.7, 2 April 2013 At line
>|336 of file scor2prt.for (unit = 10, file = '3v01.pmx')
>|
Luigi Cataldi wrote:
> > Next, when I run pmx, the pasted umlaut o
> > does get copied into the tex file, but when tex'ing the result, it is not
> > recognized at all; I don't even get a blank space. I could use what is
> > suggested in the TeXbook, i.e., \"o, and my TeX setup does recogniz
2016-02-18 17:43 GMT+02:00 Don Simons
> Next, when I run pmx, the pasted umlaut o does get copied
> into the tex file, but when tex'ing the result, it is not recognized
> at all; I don't even get a blank space.
1. Select a font (not Computer Modern) with a large character
set, e.g. Palatino (\in
> Next, when I run pmx, the pasted umlaut o
> does get copied into the tex file, but when tex'ing the result, it is not
> recognized at all; I don't even get a blank space. I could use what is
> suggested in the TeXbook, i.e., \"o, and my TeX setup does recognize that,
> but unless I do some more p
>|>
>|> Could someone familiar with Fortran explain what the
>|> "end=999" is for and why this code could fail as described
>|> in the error message?
>|
>|It means approximately this (in pseudo-Python pseudocode):
>|
>|try: read(10,'(a)')line
>|catch(EOF): goto 999
>|
>|999 is 'continue'
2016-02-18 17:48 GMT+02:00 Don Simons :
> Dirk Laurie wrote
>> It means approximately this (in pseudo-Python pseudocode):
>>
>> try: read(10,'(a)')line
>> catch(EOF): goto 999
>>
>> 999 is 'continue' so it goes on and reads again, which it is not allowed to
>> do.
>
> I disagree. I've used "contin
Don Simons wrote:
I have problems entering lower case "o" with an umlaut into pmx files, and
getting my TeX setup to recognize them. Andre has told me that he can type
one from his keyboard by hitting two keys in succession, first the umlaut,
then the "o". Problem #1 is that I do not have a key o
Don Simons wrote:
> I have problems entering lower case "o" with an umlaut into pmx files, and
> getting my TeX setup to recognize them. Andre has told me that he can type
> one from his keyboard by hitting two keys in succession, first the umlaut,
> then the "o". Problem #1 is that I do not have a
Dirk Laurie wrote
> It means approximately this (in pseudo-Python pseudocode):
>
> try: read(10,'(a)')line
> catch(EOF): goto 999
>
> 999 is 'continue' so it goes on and reads again, which it is not allowed to
> do.
I disagree. I've used "continue" hundreds of times, with the understanding that
I have problems entering lower case "o" with an umlaut into pmx files, and
getting my TeX setup to recognize them. Andre has told me that he can type
one from his keyboard by hitting two keys in succession, first the umlaut,
then the "o". Problem #1 is that I do not have a key on my keyboard with a
Bob Tennent wrote
>
> The Fortran line in question is
>
> read(10,'(a)',end=999)line
>
> Could someone familiar with Fortran explain what the "end=999" is for and
> why this code could fail as described in the error message?
>
It means if the read on unit 10 is attempted but there is nothing l
> >|At line 336 of file scor2prt.for (unit = 10, file = '3v01.pmx')
> >|Fortran runtime error: Sequential READ or WRITE not allowed after EOF
> >|marker, possibly use REWIND or BACKSPACE
> >|***
>
> The Fortran line in question is
>
> read(10,'(a)',end=999)line
>
> Could someone familiar with F
>|if I try to extract parts from the following pmx code (but this happens
>|in many other cases) with scor2prt that comes with pmx273 version I have
>|the following error:
>|
>|***
>| This is scor2prt for PMX 2.7, 2 April 2013
>|At line 336 of file scor2prt.for (unit = 10, file = '3v01.pmx')
>|pmx-2.7.3.tar.gz, the resulting scor2prt works well and
>|all is ok. But for the compilation is used f2c and not
>|gfortran (isn't true?).
Yes. This is necessary to get pmx into TeXLive.
>|If I try to compile from that source with gfortran (with
>|command "gfortran -O scor2prt.for -o scor
> Luigi, maybe scor2prt is punishing you for trying to make parts before you
> finished editing the score :-)
>
> Beyond that, I'm afraid I don't have a clue what the problem is. My version
> works fine. The only change I've made in the code in the last 3 years is to
> insert a missing type declar
18 matches
Mail list logo
