Hi, I now have a SciTE environment running on linux, but I've had to tweak some stuff, that perhaps could be backported to the distro. * Especially, setting up the font was a bit weird. The X font server (at least the free version) does not understand OpenType fonts, so I had to convert LMTypewriter10-Regular to truetype using fontforge, then install the truetype font in X. The system name became "LMTypewriter10 Regular", and the addition of " Regular" is crucial. Just "LMTypewriter10" does not work. Also, I found I needed to add an exclamation mark in from of the name to get an antialiased font (it looks awful without that). So I have changed the two lines in context.properties to: font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5 Now it works, with the exception that the top of a number of characters like [ and ] is not displayed in a most font sizes (that may be a problem caused by the auto-generated TTF font. does it happen on windows as well?). * I've changed the 'go' command so that it runs $(name.context.acrobat) $(FileName).pdf system() on unix does not automatically resolve file extensions like windows does, so the direct "$(FileName).pdf" did not work. * I also had to create texmfstart: that command does not exist on texlive (but it is in tetex 3.0). Cheers, Taco PS Shouldn't there be a cont-fr-scite.properties as well now?
Taco Hoekwater wrote:
Now it works, with the exception that the top of a number of characters like [ and ] is not displayed in a most font sizes (that may be a problem caused by the auto-generated TTF font. does it happen on windows as well?).
A problem with fontforge, it seems (is makes the descender too ). I've tried using the pfb font for a while, and that does not have this problem. However, it uses oldstyle instead of lining digits, which is just too weird for any serious editing. I guess have to find some sort of ttf -> ascii -> ttf program now. Cheers, Taco
Taco Hoekwater wrote:
Taco Hoekwater wrote:
Now it works, with the exception that the top of a number of characters like [ and ] is not displayed in a most font sizes (that may be a problem caused by the auto-generated TTF font. does it happen on windows as well?).
A problem with fontforge, it seems (is makes the descender too ). I've tried using the pfb font for a while, and that does not have this problem. However, it uses oldstyle instead of lining digits, which is just too weird for any serious editing. I guess have to find some sort of ttf -> ascii -> ttf program now.
Fixed, the ttf works fine now. saved in fontforge as svg font, edited manually, then reopened :-) Taco
Taco Hoekwater wrote:
Hi,
I now have a SciTE environment running on linux, but I've had to tweak some stuff, that perhaps could be backported to the distro.
* Especially, setting up the font was a bit weird. The X font server (at least the free version) does not understand OpenType fonts, so I had to convert LMTypewriter10-Regular to truetype using fontforge, then install the truetype font in X.
The system name became "LMTypewriter10 Regular", and the addition of " Regular" is crucial. Just "LMTypewriter10" does not work.
Also, I found I needed to add an exclamation mark in from of the name to get an antialiased font (it looks awful without that).
So I have changed the two lines in context.properties to:
font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5
so we need: if PLAT_WIN font.monospace=font:LMTypewriter10,size:16.5 font.errorfont=font:LMTypewriter10,size:11.5 if PLAT_GTK font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5
Now it works, with the exception that the top of a number of characters like [ and ] is not displayed in a most font sizes (that may be a problem caused by the auto-generated TTF font. does it happen on windows as well?).
* I've changed the 'go' command so that it runs
$(name.context.acrobat) $(FileName).pdf
system() on unix does not automatically resolve file extensions like windows does, so the direct "$(FileName).pdf" did not work.
like this? if PLAT_WIN command.go.$(file.patterns.context)=$(FileName).pdf command.go.$(file.patterns.metafun)=$(FileName).pdf command.go.$(file.patterns.example)=$(FileName).pdf command.go.*.fo=$(FileName).pdf if PLAT_GTK name.context.acrobat=acroread if PLAT_GTK command.go.$(file.patterns.context)=$(name.context.acrobat) $(FileName).pdf command.go.$(file.patterns.metafun)=$(name.context.acrobat) $(FileName).pdf command.go.$(file.patterns.example)=$(name.context.acrobat) $(FileName).pdf command.go.*.fo=$(name.context.acrobat) $(FileName).pdf
* I also had to create texmfstart: that command does not exist on texlive (but it is in tetex 3.0).
hm, that's bad news Hans
Hans Hagen wrote:
so we need:
if PLAT_WIN font.monospace=font:LMTypewriter10,size:16.5 font.errorfont=font:LMTypewriter10,size:11.5
if PLAT_GTK font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5
Not so sure. Perhaps you should not set the font on linux at all. I had to do perform quite some magic to get a usable lmtypewriter on linux, and I doubt many people will want to go through that (on X11, not setting any font is much better than attempting to set a non-existant one).
like this? ... if PLAT_GTK name.context.acrobat=acroread ...
Yes, that looks fine. Taco
Taco Hoekwater wrote:
Hans Hagen wrote:
so we need:
if PLAT_WIN font.monospace=font:LMTypewriter10,size:16.5 font.errorfont=font:LMTypewriter10,size:11.5
if PLAT_GTK font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5
can't we add your variant to the distribution (font part or tex live)? btw, such things fit into the font cd project
Not so sure. Perhaps you should not set the font on linux at all. I had to do perform quite some magic to get a usable lmtypewriter on linux, and I doubt many people will want to go through that (on X11, not setting any font is much better than attempting to set a non-existant one).
scite ignores that, at least on windows, it then uses its fall back font Hans
Hans Hagen wrote:
Taco Hoekwater wrote:
Hans Hagen wrote:
so we need:
if PLAT_WIN font.monospace=font:LMTypewriter10,size:16.5 font.errorfont=font:LMTypewriter10,size:11.5
if PLAT_GTK font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5
can't we add your variant to the distribution (font part or tex live)?
No, but I'll see if I can convince Jacko to remove the oldstyle figures from the monospace PFB default encoding. It is even possible that the wrong values are wrong in the OTF font as well, there are duplicate sets of metrics in the OTF. I'll check.
Not so sure. Perhaps you should not set the font on linux at all. I had to do perform quite some magic to get a usable lmtypewriter on linux, and I doubt many people will want to go through that (on X11, not setting any font is much better than attempting to set a non-existant one).
scite ignores that, at least on windows, it then uses its fall back font
Not on X11. I had SciTE ask for a non-existant one, and what I got was, in fact, a bold-italic sans-serif font. That's because X11 never ever returns a "font not found" error, you always get 'something'. It is possible for a program to work around this, but most programs don't bother.
Hi, SciTE is slowly growing on me. Hans, can you remove or guard these lines from context.properties, please? # WINDOWS-ONLY!! eol.mode=CRLF Some bits of my user file may be of interest: # from tex.properties, accidentally? cleaned by context.properties file.patterns.tex=*.tex;*.sty; # also from tex.properties, but with 'cls' added file.patterns.latex=*.tex;*.sty;*.aux;*.toc;*.idx;*.cls; # these were undefined, it seems filter.tex=plain TeX|$(file.patterns.tex)| filter.latex=LaTeX|$(file.patterns.latex)| # invented by me file.patterns.texmplog=*.log;*.blg;*.ilg;*.err;*.fls filter.log=TeX&MP logs|$(file.patterns.texmplog)| open.filter=$(all.files)\ # ....................... # ........... # personal preference: i like tabs tabbar.hide.one=0 # rxvt is a reasonable default on linux name.context.console=rxvt # but konsole is the kde terminal, and I like that even better name.context.console=konsole # the shell script to call xpdf in server mode name.context.acrobat=xpdfopen # patched texexec name.context.texexec=texmfstart texexec.pl --xpdf # bugfix for Gtk version of SciTE command.compile.$(file.patterns.context)= \ $(name.context.texexec) --pdf $(FileNameExt) command.build.$(file.patterns.context)= \ $(name.context.texexec) --autopdf --pdf $(FileNameExt) I had to create separate compile and build commands. With SciTE on linux, when the pdf browser is started from within texexec, the build command never exits: the menu remain disabled after the first run, until such time as you quit the browser manually. It does not matter whether texmfstart returns to the commandline, Scite waits for all the (grand)children to exit. Setting command.build.subsystem.$(file.patterns.context)=2 does not help, because then I get nothing in the output window. So now I do first Ctrl-f7 (compile), then F5 (go), then F7 thereafter. Not ideal, but I could not come up with a better solution. Hans Hagen wrote:
Taco Hoekwater wrote:
Hans Hagen wrote:
so we need:
if PLAT_WIN font.monospace=font:LMTypewriter10,size:16.5 font.errorfont=font:LMTypewriter10,size:11.5
if PLAT_GTK font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5
can't we add your variant to the distribution (font part or tex live)?
btw, such things fit into the font cd project
Not so sure. Perhaps you should not set the font on linux at all. I had to do perform quite some magic to get a usable lmtypewriter on linux, and I doubt many people will want to go through that (on X11, not setting any font is much better than attempting to set a non-existant one).
scite ignores that, at least on windows, it then uses its fall back font
Hans
Taco Hoekwater wrote:
SciTE is slowly growing on me. Hans, can you remove or guard these lines from context.properties, please?
# WINDOWS-ONLY!! eol.mode=CRLF
ok
Some bits of my user file may be of interest:
# from tex.properties, accidentally? cleaned by context.properties file.patterns.tex=*.tex;*.sty;
not here
# also from tex.properties, but with 'cls' added file.patterns.latex=*.tex;*.sty;*.aux;*.toc;*.idx;*.cls;
ok
# these were undefined, it seems filter.tex=plain TeX|$(file.patterns.tex)| filter.latex=LaTeX|$(file.patterns.latex)|
i hope that does not clash
# invented by me file.patterns.texmplog=*.log;*.blg;*.ilg;*.err;*.fls filter.log=TeX&MP logs|$(file.patterns.texmplog)|
isn't that: filter.texmplog
open.filter=$(all.files)
?
\ # ....................... # ...........
# personal preference: i like tabs tabbar.hide.one=0
what does this one do?
# rxvt is a reasonable default on linux name.context.console=rxvt # but konsole is the kde terminal, and I like that even better name.context.console=konsole
ok
# the shell script to call xpdf in server mode name.context.acrobat=xpdfopen
ok
# patched texexec name.context.texexec=texmfstart texexec.pl --xpdf
ok, i introduced name.texexec.flag.pdfopen=--autopdf --xpdf
# bugfix for Gtk version of SciTE command.compile.$(file.patterns.context)= \ $(name.context.texexec) --pdf $(FileNameExt) command.build.$(file.patterns.context)= \ $(name.context.texexec) --autopdf --pdf $(FileNameExt)
I had to create separate compile and build commands. With SciTE on linux, when the pdf browser is started from within texexec, the build command never exits: the menu remain disabled after the first run, until such time as you quit the browser manually. It does not matter whether texmfstart returns to the commandline, Scite waits for all the (grand)children to exit.
so maybe it's better in gtk mode to omit --autopdf ?
Setting
command.build.subsystem.$(file.patterns.context)=2
does not help, because then I get nothing in the output window. So now I do first Ctrl-f7 (compile), then F5 (go), then F7 thereafter.
Not ideal, but I could not come up with a better solution.
Hans Hagen wrote:
Taco Hoekwater wrote:
Hans Hagen wrote:
so we need:
if PLAT_WIN font.monospace=font:LMTypewriter10,size:16.5 font.errorfont=font:LMTypewriter10,size:11.5
if PLAT_GTK font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5
can't we add your variant to the distribution (font part or tex live)?
btw, such things fit into the font cd project
Not so sure. Perhaps you should not set the font on linux at all. I had to do perform quite some magic to get a usable lmtypewriter on linux, and I doubt many people will want to go through that (on X11, not setting any font is much better than attempting to set a non-existant one).
scite ignores that, at least on windows, it then uses its fall back font
Hans
-- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hans Hagen wrote:
# invented by me file.patterns.texmplog=*.log;*.blg;*.ilg;*.err;*.fls filter.log=TeX&MP logs|$(file.patterns.texmplog)|
isn't that: filter.texmplog
I could have named it that.
open.filter=$(all.files)
?
The default one starts with $(all.source), and I often need to see everything, not just 'registered' files.
tabbar.hide.one=0
what does this one do?
If it is set to 1, there is no tabbar when only one document is open. But that makes the document jump up and down when you switch from one to two open documents and back, which I don't like.
I had to create separate compile and build commands. With SciTE on linux, when the pdf browser is started from within texexec, the build command never exits: the menu remain disabled after the first run, until such time as you quit the browser manually. It does not matter whether texmfstart returns to the commandline, Scite waits for all the (grand)children to exit.
so maybe it's better in gtk mode to omit --autopdf ?
Maybe so. My setup works for me, but not for the general public, I guess. Cheers, Taco
Taco Hoekwater wrote:
Maybe so. My setup works for me, but not for the general public, I guess.
i added most of what you want, the rest can then be configured (overloaded) in the user.properties file; that's the nice things about scite Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi again, I've found this little thingy useful: command.name.26.*=Open Logfile command.subsystem.26.*=3 command.26.*=open_log command.save.before.26.*=2 command.groupundo.26.*=yes command.shortcut.26.*=Ctrl+L function open_log() scite.Open(props['FileName'] .. ".log") end Cheers, Taco Hans Hagen wrote:
i added most of what you want, the rest can then be configured (overloaded) in the user.properties file; that's the nice things about scite
Taco Hoekwater wrote:
Hi again,
I've found this little thingy useful:
command.name.26.*=Open Logfile command.subsystem.26.*=3 command.26.*=open_log command.save.before.26.*=2 command.groupundo.26.*=yes command.shortcut.26.*=Ctrl+L
function open_log() scite.Open(props['FileName'] .. ".log") end
ok, added; but Ctrl+E instead (ctrl-l is too handy) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (2)
-
Hans Hagen -
Taco Hoekwater