You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(16) |
Apr
(100) |
May
(78) |
Jun
(44) |
Jul
(86) |
Aug
(56) |
Sep
(29) |
Oct
(70) |
Nov
(110) |
Dec
(104) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(189) |
Feb
(77) |
Mar
(90) |
Apr
(101) |
May
(79) |
Jun
(96) |
Jul
(220) |
Aug
(90) |
Sep
(117) |
Oct
(152) |
Nov
(77) |
Dec
(62) |
2006 |
Jan
(71) |
Feb
(149) |
Mar
(144) |
Apr
(156) |
May
(56) |
Jun
(149) |
Jul
(38) |
Aug
(90) |
Sep
(49) |
Oct
(71) |
Nov
(67) |
Dec
(100) |
2007 |
Jan
(76) |
Feb
(52) |
Mar
(73) |
Apr
(96) |
May
(88) |
Jun
(88) |
Jul
(155) |
Aug
(139) |
Sep
(54) |
Oct
(174) |
Nov
(217) |
Dec
(93) |
2008 |
Jan
(125) |
Feb
(161) |
Mar
(69) |
Apr
(54) |
May
(85) |
Jun
(134) |
Jul
(143) |
Aug
(98) |
Sep
(82) |
Oct
(131) |
Nov
(147) |
Dec
(189) |
2009 |
Jan
(61) |
Feb
(71) |
Mar
(86) |
Apr
(51) |
May
(78) |
Jun
(102) |
Jul
(98) |
Aug
(88) |
Sep
(140) |
Oct
(22) |
Nov
(18) |
Dec
(24) |
2010 |
Jan
(11) |
Feb
(43) |
Mar
(23) |
Apr
(39) |
May
(46) |
Jun
(34) |
Jul
(17) |
Aug
(16) |
Sep
(46) |
Oct
(48) |
Nov
(29) |
Dec
(58) |
2011 |
Jan
(35) |
Feb
(83) |
Mar
(41) |
Apr
(33) |
May
(23) |
Jun
(39) |
Jul
(6) |
Aug
(23) |
Sep
(30) |
Oct
(22) |
Nov
(68) |
Dec
(55) |
2012 |
Jan
(43) |
Feb
(40) |
Mar
(28) |
Apr
(9) |
May
(96) |
Jun
(54) |
Jul
(468) |
Aug
(678) |
Sep
(640) |
Oct
(112) |
Nov
(60) |
Dec
(154) |
2013 |
Jan
(113) |
Feb
(50) |
Mar
(74) |
Apr
(17) |
May
(45) |
Jun
(32) |
Jul
(52) |
Aug
(16) |
Sep
(66) |
Oct
(60) |
Nov
(64) |
Dec
(62) |
2014 |
Jan
(43) |
Feb
(25) |
Mar
(29) |
Apr
(9) |
May
(5) |
Jun
(60) |
Jul
(31) |
Aug
(42) |
Sep
(19) |
Oct
(13) |
Nov
(9) |
Dec
(2) |
2015 |
Jan
(45) |
Feb
(29) |
Mar
(8) |
Apr
(2) |
May
(10) |
Jun
(8) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(7) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
(4) |
Apr
(43) |
May
(2) |
Jun
(20) |
Jul
(7) |
Aug
(39) |
Sep
(20) |
Oct
(11) |
Nov
(9) |
Dec
|
2017 |
Jan
(3) |
Feb
|
Mar
(4) |
Apr
(1) |
May
(2) |
Jun
(16) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(10) |
Apr
(1) |
May
(16) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(7) |
2019 |
Jan
(3) |
Feb
(4) |
Mar
(7) |
Apr
(20) |
May
|
Jun
(10) |
Jul
(15) |
Aug
(19) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
(15) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Chanop Silpa-A. <ch...@sy...> - 2004-06-18 02:55:45
|
Hi Paul, My friend, on the other day, asked me to package mensis for Debian. I will try to bundle mensis with FontForge (for experiment) with my next Debian upload then. Cheers, Chanop On a good day of Fri, Jun 18, 2004 at 01:18:32AM +0100, Paul LeoNerd Evans = wrote > Yes; mensis looks a most useful program. However, my current installation > of fontforge is a debian package, rather than built-from-source. This > causes some difficulty in compiling mensis; which currently isn't > debian-compiled. How do you suggest I do this?=20 |
From: Paul L. E. <le...@le...> - 2004-06-18 00:18:49
|
On 17 Jun 2004 13:08:00 -0700 George Williams <gw...@si...> wrote: <a long and informative discussion of typesetting details> > My guess is that xterm is using the WinAscent/WinDescent fields, so you > can try experimenting with modifying these fields. The program mensis > (http://mensis.sf.net/) will allow you to view and manipulate these > fields directly. Yes; mensis looks a most useful program. However, my current installation of fontforge is a debian package, rather than built-from-source. This causes some difficulty in compiling mensis; which currently isn't debian-compiled. How do you suggest I do this? Should it be sufficient to compile against latest fontforge sources, but keep installed libraries and binaries from debian, or should I remove debian's package and go completely from-source? -- Paul "LeoNerd" Evans le...@le... ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/ |
From: George W. <gw...@si...> - 2004-06-17 20:06:03
|
On Thu, 2004-06-17 at 11:00, Paul LeoNerd Evans wrote: > [I posted this bug to the website and as yet have received no reply; I > thought I'd post it to the mailing list too, since I've just found it, > to see what suggestions anyone might have] Yup, the sourceforge bug list gets ignored. All bugs should be reported to the mailing list. > If I just open up the original .TTF file, set a new > name in the Font Info page, and re-export it out as a > .TTF file, the new font generates lines that are > somewhat taller than the original. I've compared the > ascent, descent and line gap parameters between the two > fonts, again in the Font Info page, and I can't see any > differences. Though, I have no other font editor by > which to compare them.. there may be some subtle > differences I can't see... > > It appears that only Xterm is affected by this; in both > gvim and OpenOffice the original and new fonts look > identical. > Any thougts anyone? At least, any way I can find out whether this is a > FontForge, or an Xterm issue? I can tell you where the problem is likely to lie. Though I'm not familiar enough with the guts of xterm or OpenOffice or gvim to say exactly what they do. In the open/truetype spec there are three or four different values that can be used to generate inter-line spacing. In conventional typography the (unleaded) interline spacing of a 12pt font was 12pts. That was the definition of a 12pt font, each glyph was carved on a block of metal that was 12pts high. The 'head' table contains the font's bounding box, and this could be used for line spacing (though it isn't supposed to be). The 'hhea' table contains the macintosh typographic ascent/descent/ linegap. This is only used on the mac, as far as I know. The 'OS/2' table contains two sets of extremely badly documented values that could be used to set the interline spacing under windows. One set is called TypoAscender/TypoDescender/TypoLineGap and is supposed to be used for this purpose. There are also the WinAscent/WinDescent fields which have been documented in such a contradictory way that it isn't clear what they should be set to nor what they mean, nor why they are present at all. The documentation states: Some applications use this value (WinAscent) to determine default line spacing. This is strongly discouraged. The typographic ascender, descender and line gap fields in conjunction with unitsPerEm should be used for this purpose. FontForge sets the TypoAscender to the Ascent value specified in Element->FontInfo->General by default FontForge sets the WinAscent value to the ymax of the font's bounding box (anything less and some glyphs in the font will be clipped). You can adjust this from Element->FontInfo->TTF Values (or at least you can in recent builds) My guess is that xterm is using the WinAscent/WinDescent fields, so you can try experimenting with modifying these fields. The program mensis (http://mensis.sf.net/) will allow you to view and manipulate these fields directly. |
From: Paul L. E. <le...@le...> - 2004-06-17 18:00:11
|
[I posted this bug to the website and as yet have received no reply; I thought I'd post it to the mailing list too, since I've just found it, to see what suggestions anyone might have] ----- [[ BUG ID 956234 ]] Re-export TTF changes line spacing I'm trying to edit the Bistream Vera Sans Mono font to add some new glyphs that are useful in Xterms, as well as generate more of the combined accent glpyhs automatically, but I keep coming up against a problem. If I just open up the original .TTF file, set a new name in the Font Info page, and re-export it out as a .TTF file, the new font generates lines that are somewhat taller than the original. I've compared the ascent, descent and line gap parameters between the two fonts, again in the Font Info page, and I can't see any differences. Though, I have no other font editor by which to compare them.. there may be some subtle differences I can't see... It appears that only Xterm is affected by this; in both gvim and OpenOffice the original and new fonts look identical. ----- Any thougts anyone? At least, any way I can find out whether this is a FontForge, or an Xterm issue? -- Paul "LeoNerd" Evans le...@le... ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/ |
From: kovzol <ko...@ma...> - 2004-06-16 09:00:10
|
> | Arial but I need a Condensed version of it. > > What about > > http://www.gust.org.pl/fonty/ Great idea! Thank you! I downloaded it and tried out. It works perfectly and contains all the characters we currently need. :-) Zoltan |
From: George W. <gw...@si...> - 2004-06-15 19:49:38
|
On Tue, 2004-06-15 at 00:10, Pierre Hanser wrote: > It seems that in bvedit.c, in BCPasteInto variable x is not initialized. True. And there's another bug when dealing with greymaps. > I've also an other problem, but which is less interesting, it seems > that it is not possible to 'look for problems' in a font which has no > space character. I was trying this on a font extract which is not > a "real font", so it's not so a real problem. There should be no dependence on a font having a space. If you have a font where find problems does not work, please send it to me. |
From: Pierre H. <ha...@cl...> - 2004-06-15 07:20:08
|
Le Dimanche 13 Juin 2004 02:26, George Williams a =E9crit : > On Sat, 2004-06-12 at 05:54, Pierre Hanser wrote: > > Experimenting with BDF files, it seems that what Fonforge uses > > for 'Width' comes from the swidth field of the BDF file. But it > > seems that this field is very often less accurate than the pixel > > width which can be found in dwidth field. I even have a font where > > all swidth fields are '1'. > > > > I wonder if Fontforge should not have a way to recalculate the swidth > > when it's so badly broken. > > > > What do you think about this? > > My intent is that FontForge primarily be an outline font editor. As such > the SWIDTH field should be the more important value. > > X is moving away from BDF, and I don't think anyone else really uses > them. So I don't want to put much energy into fixing bad BDF files. I understand and agree with your position. But as I'm working on embedded systems, it's sometimes necessary to use pixel fonts... So I decided to make an external script to correct this kind= of=20 problems. Issue solved. =2D-=20 Pierre Hanser |
From: Pierre H. <ha...@cl...> - 2004-06-15 07:15:24
|
hello This morning I've a problem building accented chars: Fontforge crashes. It seems that in bvedit.c, in BCPasteInto variable x is not initialized. I've also an other problem, but which is less interesting, it seems that it is not possible to 'look for problems' in a font which has no space character. I was trying this on a font extract which is not a "real font", so it's not so a real problem. Have a good day =2D-=20 Pierre Hanser |
From: George W. <gw...@si...> - 2004-06-13 00:24:24
|
On Sat, 2004-06-12 at 05:54, Pierre Hanser wrote: > Experimenting with BDF files, it seems that what Fonforge uses > for 'Width' comes from the swidth field of the BDF file. But it > seems that this field is very often less accurate than the pixel > width which can be found in dwidth field. I even have a font where > all swidth fields are '1'. > > I wonder if Fontforge should not have a way to recalculate the swidth > when it's so badly broken. > > What do you think about this? My intent is that FontForge primarily be an outline font editor. As such the SWIDTH field should be the more important value. X is moving away from BDF, and I don't think anyone else really uses them. So I don't want to put much energy into fixing bad BDF files. |
From: Pierre H. <ha...@cl...> - 2004-06-12 12:57:22
|
hello Experimenting with BDF files, it seems that what Fonforge uses for 'Width' comes from the swidth field of the BDF file. But it seems that this field is very often less accurate than the pixel width which can be found in dwidth field. I even have a font where all swidth fields are '1'. I wonder if Fontforge should not have a way to recalculate the swidth when it's so badly broken. What do you think about this? =2D-=20 Pierre Hanser |
From: <las...@tv...> - 2004-06-12 11:10:58
|
kovzol wrote: >Hello, > >I also installed FontForge. Now I can scale single characters, but not all >of them in the same time. Is it possible? > > > Hi, Wooh, it is a good news that other people are using FontForge in Szeged. Although I am very busy this summer I can help you to create a good condensed font for your mathematical application. I have been using FontForge for a long while so I think I can work fast with it. I share George's opinion that it is not a good idea to make a condensed font from a normal one using a simple script. You should take a free condensed font (it is enough if covers only latin1) and make a derivation in order to meet all your requirements. Włodek's suggestion (qhvcr) seems to be a good alternative. However, it needs a minimal work because it did not seem to me as a fully unicode compatible font. Feel free to ask me, of course in Hungarian :-) Laci (University of Szeged, Department of Altaic Studies) |
From: George W. <gw...@si...> - 2004-06-12 04:42:30
|
On Fri, 2004-06-11 at 14:08, Ben Crowell wrote: > BTW, I forgot to tell you what version it was: pfaedit-031029. But... > Simplifying font... Copyright (c) 2000-2004 by George Williams. > Executable based on sources from 12:29 4-Apr-2004. > FontForge used to be named PfaEdit. It looks like fontforge-20040404... > stack trace. Unfortunately, it looks to me like it didn't get compiled with the > symbols in the executable, so the stack trace isn't very informative -- No it isn't. I assume the arguments to fontforge should be fontforge -script simplify.pe before-pfaedit.pfx feta11.tfm This does not crash in the current build. There have been a number of fixes in tfm handling which might account for it, or there may be something else going on which I'm not aware of. I suggest you try downloading http://fontforge.sf.net/fontforge_full-20040601.tgz and see if you can reproduce the bug in it. |
From: George W. <gw...@si...> - 2004-06-11 20:15:09
|
On Thu, 2004-06-10 at 16:55, Ben Crowell wrote: > FontForge is crashing on my FreeBSD 5.2 system when I try to install the lilypond > music typesetting program. I'm confused. Are you saying that fontforge ran before you installed lilypond and crashed thereafter? > Dunno if a FreeBSD core dump would be of any use to you, Nope, but if you can run it in gdb and give me a stack trace that might be helpful. $ gdb fontforge (gdb) r [whatever arguments you normally give fontforge] [do whatever you normally do until it crashes] (gdb) where (gdb) ^D > but in any case I can't seem to find where the core file was left -- maybe the > makefile automatically cleans it up or something. Or are you saying that the fontforge install itself crashes? I have no idea where FreeBsd puts core files. > |
From: <ma...@un...> - 2004-06-11 20:05:33
|
| We need Helvetica Condensed or a similar font for our dynamically created | web page. Unfortunately, Helvetica is not free for use but our software | must contain only free components. My idea is to substitute Helvetica with | Arial but I need a Condensed version of it. What about http://www.gust.org.pl/fonty/ (QuasiSwiss and QuasiSwissCondensed -- these are free versions of Helvetica). All the fonts mentioned on the above page are available on any CTAN server, for example ftp://ftp.dante.de/tex-archive/fonts/psfonts/polish/qfonts. --Wlodek Bzyl |
From: George W. <gw...@si...> - 2004-06-11 20:04:34
|
On Fri, 2004-06-11 at 03:35, kovzol wrote: > I also installed FontForge. Now I can scale single characters, but not all > of them in the same time. Is it possible? Please use FontForge rather than PfaEdit now. >From the character view you can scale that character. From the font view you can select multiple characters and scale them all. |
From: kovzol <ko...@ma...> - 2004-06-11 10:38:06
|
Hello, I also installed FontForge. Now I can scale single characters, but not all of them in the same time. Is it possible? TIA, Zoltan Kova'cs Zolta'n assistant teacher at Bolyai Institute ko...@ma... http://www.math.u-szeged.hu/~kovzol ---------- Forwarded message ---------- Date: Fri, 11 Jun 2004 10:54:19 +0200 (CEST) From: kovzol <ko...@ma...> To: pfa...@li... Cc: pf...@us..., mol...@ax..., va...@ma... Subject: generating Arial Condensed font Hello, I'm new to PFAedit, but it seems to be a great software. Let me introduce myself. I'm also a software developer, I am the project leader of the WebMathematics Interactive web portal (http://wmi.sf.net). We need Helvetica Condensed or a similar font for our dynamically created web page. Unfortunately, Helvetica is not free for use but our software must contain only free components. My idea is to substitute Helvetica with Arial but I need a Condensed version of it. Arial is also copyrighted but it is free for normal use IMHO. My idea is to convert the normal Arial font to a condensed/narrow version of it using PFAedit, but your software is too complex for me. Is it possible to do it in 5 minutes of work? Or, if not, do you have any free alternative of Helvetica Condensed? Thank you in advance. Yours sincerely, Zoltan Kovacs assistant teacher Bolyai Institute, Szeged, Hungary http://www.math.u-szeged.hu/~kovzol |
From: Ben C. <cro...@li...> - 2004-06-10 23:53:23
|
Hi, This is probably not going to be the best bug report ever written, but I thought I'd at least give you a heads-up to let you know that the problem exists. Basically FontForge is crashing on my FreeBSD 5.2 system when I try to install the lilypond music typesetting program. Dunno if a FreeBSD core dump would be of any use to you, but in any case I can't seem to find where the core file was left -- maybe the makefile automatically cleans it up or something. Please let me know if you'd like me to do anything on my end to help you track the problem down, but I don't program much in C, and don't know gdb. Regards, Ben Crowell ------------------------------------------------------------------------------------ [snip] mftrace 1.0.29 Font `feta11'... /usr/local/lib/python2.3/site-packages/tfm.py:8: FutureWarning: x<<y losing bits or changing sign will return a long in Python 2.4 and up cs = cs + (ord (b) << shift) Using encoding file: `./out/feta11.enc' Running Metafont... Tracing bitmaps... [33][34][35][36][37][38][39][40][41][42][43][44][45][46][47][48][49][50][51][52][53][54][55][56][57][58][59][60][61][62][63][64][65][66][67][68][69][70][71][72][73][74][75][76][77][78][79][80][81][82][83][84][85][86][87][88][89][90][91][92][93][94][95][96][97][98][99][100][101][102][103][104][105][106][107][108][109][110][111][112][113][114][115][116][117][118][119][120][121][122][123][124][125][126][127][128][129][130][131][132][133][134][135][136][137][138][139][140][141][142][143][144][145][146][147][148][149][150][151][152][153][154][155][156][157][158][159][160][161][162][163][164][165][166][167][168][169][170][171][172][173][174][175][176][177][178][179][180][181][182][183][184][185][186][187][188][189][190] Assembling font to `feta11.pfa'... Simplifying font... Copyright (c) 2000-2004 by George Williams. Executable based on sources from 12:29 4-Apr-2004. FontForge used to be named PfaEdit. Bus error (core dumped) error: fontforge: command exited with value 35328 Traceback (most recent call last): File "/usr/local/bin/mftrace", line 1155, in ? cleanup_font (basename + '.pfa') File "/usr/local/bin/mftrace", line 815, in cleanup_font system ("%s -script simplify.pe %s %s" % (fontforge_cmd, file, tfmfile)) File "/usr/local/bin/mftrace", line 243, in system error (msg) File "/usr/local/bin/mftrace", line 134, in error raise _ ("Exiting ... ") Exiting ... gmake[1]: *** [out/feta11.pfa] Error 1 gmake[1]: Leaving directory `/usr/ports/print/lilypond/work/lilypond-2.0.3/mf' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/print/lilypond. |
From: George W. <gw...@si...> - 2004-06-10 20:45:43
|
On Thu, 2004-06-10 at 11:37, Pierre Hanser wrote: > I'm working with BDF files through scripts, and I've realized that the > resolution parameter in the Generate command is currently ignored in this > case. I'm afraid you are right. |
From: Pierre H. <ha...@cl...> - 2004-06-10 18:40:29
|
hello I'm working with BDF files through scripts, and I've realized that the=20 resolution parameter in the Generate command is currently ignored in this case. It seems that 'ask_user_for_resolution' should be reset in bGenerate to get the resolution taken into account. I wonder if this is intended or not, as in fact the resolution coded into a BDF font is not used by the application I'm using today... Good evening to all =2D-=20 Pierre Hanser |
From: Chanop Silpa-A. <ch...@sy...> - 2004-06-10 06:14:09
|
On a good day of Thu, Jun 10, 2004 at 04:04:35PM +1000, Chanop Silpa-Anan wrote > I, however, use Xft from darwinport, because at one point (in the > beginning), I could not get Apple's Xft to work with fontforge properly. ^^^^^^^^^ Oops, wrong, that must be gtk library. What I meant was that I could not get Apple's freetype to work properly with fontforge. Chanop -- ######################################### #Chanop Silpa-Anan # #gpg @ http://thai.anu.edu.au/chanop.asc# ######################################### |
From: Chanop Silpa-A. <ch...@sy...> - 2004-06-10 06:04:41
|
George, Xft is in X11. X11User.pkg: ./usr/X11R6/lib/X11/doc/html/Xft.3.html 100444 0/0 8940 1991868780 ./usr/X11R6/lib/libXft.1.1.dylib 100644 0/0 55520 292103580 ./usr/X11R6/lib/libXft.1.dylib 120755 0/0 16 3187334349 libXft.1.1.dylib ./usr/X11R6/lib/libXft.2.1.dylib 100644 0/0 72812 1639309002 ./usr/X11R6/lib/libXft.2.dylib 120755 0/0 16 948576723 libXft.2.1.dylib ./usr/X11R6/lib/libXft.dylib 120755 0/0 16 948576723 libXft.2.1.dylib X11SDK.pkg: ./usr/X11R6/include/X11/Xft 40755 0/0 ./usr/X11R6/include/X11/Xft/Xft.h 100444 0/0 12606 539400434 ./usr/X11R6/include/X11/Xft/XftCompat.h 100444 0/0 5399 62636825 ./usr/X11R6/lib/libXft.a 100644 0/0 101700 2114725855 ./usr/X11R6/man/man3/Xft.3 100444 0/0 5717 3028085605 I, however, use Xft from darwinport, because at one point (in the beginning), I could not get Apple's Xft to work with fontforge properly. I can try digging the issue up again if you would like. Chanop On a good day of Wed, Jun 09, 2004 at 10:17:32PM -0700, George Williams wrote > If anyone on the list has OS/X 10.3 with Apple's version of X11 > installed, can you tell me if Xft is included in their X11? -- ######################################### #Chanop Silpa-Anan # #gpg @ http://thai.anu.edu.au/chanop.asc# ######################################### |
From: George W. <gw...@si...> - 2004-06-10 05:15:34
|
If anyone on the list has OS/X 10.3 with Apple's version of X11 installed, can you tell me if Xft is included in their X11? |
From: Werner L. <wl...@gn...> - 2004-06-09 05:21:39
|
I just received this message which could be of interest for you. Werner |
From: George W. <gw...@si...> - 2004-06-03 22:54:02
|
On Thu, 2004-06-03 at 15:03, Andrey V. Panov wrote: > On Wednesday 02 June 2004 11:57, George Williams wrote: > > On Tue, 2004-06-01 at 17:48, Andrey V. Panov wrote: > > > Could you add possibility to change "Accent offset percent" parameter > > > using BuildAccented() script command as second argument without change of > > > preferences? And also possibly to change other parameters: > > > "AccentcenterLowest" and "CharCenterHighest". > > > > I don't think so. It's easy enough to change the preferences. > > > > It is not possible to access these parameters from a script. Sorry, there was a typo, it should be possible to access these prefs just like any other ones. |
From: Andrey V. P. <pa...@ca...> - 2004-06-03 22:04:09
|
On Wednesday 02 June 2004 11:57, George Williams wrote: > On Tue, 2004-06-01 at 17:48, Andrey V. Panov wrote: > > Could you add possibility to change "Accent offset percent" parameter > > using BuildAccented() script command as second argument without change of > > preferences? And also possibly to change other parameters: > > "AccentcenterLowest" and "CharCenterHighest". > > I don't think so. It's easy enough to change the preferences. > It is not possible to access these parameters from a script. -- Andrey V. Panov panov /@/ canopus.iacp.dvo.ru |