<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sciteco/lib/lexers/woman.tes, branch v2.5.0</title>
<subtitle>Scintilla-based Text Editor and COrrector</subtitle>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/'/>
<entry>
<title>&lt;EI&gt; has been repurposed and is the macro file inclusion (indirect file) command now</title>
<updated>2025-05-24T14:22:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-05-24T13:24:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=6e3da17a2fae11af9ae00d9b59bd0d752022e16b'/>
<id>6e3da17a2fae11af9ae00d9b59bd0d752022e16b</id>
<content type='text'>
* Improves DEC TECO-11 compatibility.
* &lt;EM&gt; is still supported as a synonym, but considered deprecated and is no longer documented.
  A warning is printed when invoked.
  It can be repurposed at any time in the future.
* `EI$` is not yet supported.
  I am unsure whether this makes any sense.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Improves DEC TECO-11 compatibility.
* &lt;EM&gt; is still supported as a synonym, but considered deprecated and is no longer documented.
  A warning is printed when invoked.
  It can be repurposed at any time in the future.
* `EI$` is not yet supported.
  I am unsure whether this makes any sense.
</pre>
</div>
</content>
</entry>
<entry>
<title>Gtk: monospaced sections in womanpages now respect lexer.font and variable-width font is configurable via lexer.woman.font (refs #34)</title>
<updated>2025-04-22T17:50:48+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-04-22T17:50:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=93d3cbd390e65576d0c8740233b0a7569d9bdd89'/>
<id>93d3cbd390e65576d0c8740233b0a7569d9bdd89</id>
<content type='text'>
* grosciteco was just hardcoding "Monospace", regardless of what was configured via lexer.font in ~/.teco_ini
* The variable-width font used for ordinary "womanpage" body texts was hardcoded to "Serif".
  It is now configurable via the lexer.woman.font register.
* There is a difference, though:
  lexer.font has no default value and must therefore be checked everywhere.
  This is so you can set it even before munging lexer.tes.
  lexer.woman.font however has a default (Serif), so it can only be overridden after
  munging lexer.tes.
  Perhaps it would be easier and more consistent to have a default for lexer.font as well.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* grosciteco was just hardcoding "Monospace", regardless of what was configured via lexer.font in ~/.teco_ini
* The variable-width font used for ordinary "womanpage" body texts was hardcoded to "Serif".
  It is now configurable via the lexer.woman.font register.
* There is a difference, though:
  lexer.font has no default value and must therefore be checked everywhere.
  This is so you can set it even before munging lexer.tes.
  lexer.woman.font however has a default (Serif), so it can only be overridden after
  munging lexer.tes.
  Perhaps it would be easier and more consistent to have a default for lexer.font as well.
</pre>
</div>
</content>
</entry>
<entry>
<title>Gtk/win32: fixed fonts and therefore pango warnings on startup (closes #7)</title>
<updated>2025-04-18T18:27:00+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-04-18T18:27:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=91fa1656600a52eddf650ea550e7cbd69d72903e'/>
<id>91fa1656600a52eddf650ea550e7cbd69d72903e</id>
<content type='text'>
* The default womanpage font is the abstract "Serif" now, so that should be
  more portable. "Times" wasn't found on Windows.
* Win32 distributions include a custom .teco_css now, which
  removes the small-caps font attribute from the type label.
  The default Gtk theme on Windows references the "Segoe UI" font
  and it doesn't have a small-caps variant.
  In fact no default Windows font appears to have one.
* We could add a custom .teco_ini to win32 distributions as well,
  but there is currently no need for it.
* Do not distribute the /win32 files. They are used only for building
  Win32/64 packages. There is no point in distributing them in the tarball if
  the /debian and /freebsd directories aren't distributed as well.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* The default womanpage font is the abstract "Serif" now, so that should be
  more portable. "Times" wasn't found on Windows.
* Win32 distributions include a custom .teco_css now, which
  removes the small-caps font attribute from the type label.
  The default Gtk theme on Windows references the "Segoe UI" font
  and it doesn't have a small-caps variant.
  In fact no default Windows font appears to have one.
* We could add a custom .teco_ini to win32 distributions as well,
  but there is currently no need for it.
* Do not distribute the /win32 files. They are used only for building
  Win32/64 packages. There is no point in distributing them in the tarball if
  the /debian and /freebsd directories aren't distributed as well.
</pre>
</div>
</content>
</entry>
<entry>
<title>womanpage lexer: fixed popup styling</title>
<updated>2016-11-22T21:33:36+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2016-11-22T21:33:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=0fbbc0d99625e00e5a0389e28fc8dcd4160aeac2'/>
<id>0fbbc0d99625e00e5a0389e28fc8dcd4160aeac2</id>
<content type='text'>
 * the ESSTYLECLEARALL$$ was resetting the STYLE_CALLTIP
   (and others) resulting in wrongly-styled popups.
 * We now only change STYLE_DEFAULT for Gtk UIs and
   use `color.init` to reinitialize the other styles
   (not very elegant).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
 * the ESSTYLECLEARALL$$ was resetting the STYLE_CALLTIP
   (and others) resulting in wrongly-styled popups.
 * We now only change STYLE_DEFAULT for Gtk UIs and
   use `color.init` to reinitialize the other styles
   (not very elegant).
</pre>
</div>
</content>
</entry>
<entry>
<title>implemented self-documenting (online) help system</title>
<updated>2016-11-18T06:05:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2016-02-26T01:02:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=e7867fb0d9979c550e6e3d7597ece73b680c4af6'/>
<id>e7867fb0d9979c550e6e3d7597ece73b680c4af6</id>
<content type='text'>
 * the new "?" (help) command can be used to look up
   help topics.
 * help topics are index from $SCITECOPATH/women/*.woman.tec
   files.
 * looking up a help topic opens the corresponding "womanpage"
   and jumps to the position of the topic (it acts like an anchor
   into the document).
 * styling is performed by *.woman.tec files.
 * Setting up the Scintilla view and munging the *.tec file
   is performed by the new "woman.tes" lexer.
   On supporting UIs (Gtk), womanpages are shown in a variable-width
   font.
 * Woman pages are usually not hand-written, but generated from manpages.
   A special Groff post-processor grosciteco has been introduced for this
   purpose. It is much like grotty, but can output SciTECO macros for styling
   the document (ie. the *.woman.tec files).
   It is documented in its own man-page.
 * grosciteco also introduces sciteco.tmac - special Troff macros
   for controlling the formatting of the document in SciTECO.
   It also defines .SCITECO_TOPIC which can be used to mark up
   help topics/terms in Troff markup.
 * Woman pages are generated/formatted by grosciteco at compile-time, so
   they will work on platforms without Groff (ie. as on windows).
 * Groff has been added as a hard compile-time requirement.
 * The sciteco(1) and sciteco(7) man pages have been augmented with
   help topic anchors.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
 * the new "?" (help) command can be used to look up
   help topics.
 * help topics are index from $SCITECOPATH/women/*.woman.tec
   files.
 * looking up a help topic opens the corresponding "womanpage"
   and jumps to the position of the topic (it acts like an anchor
   into the document).
 * styling is performed by *.woman.tec files.
 * Setting up the Scintilla view and munging the *.tec file
   is performed by the new "woman.tes" lexer.
   On supporting UIs (Gtk), womanpages are shown in a variable-width
   font.
 * Woman pages are usually not hand-written, but generated from manpages.
   A special Groff post-processor grosciteco has been introduced for this
   purpose. It is much like grotty, but can output SciTECO macros for styling
   the document (ie. the *.woman.tec files).
   It is documented in its own man-page.
 * grosciteco also introduces sciteco.tmac - special Troff macros
   for controlling the formatting of the document in SciTECO.
   It also defines .SCITECO_TOPIC which can be used to mark up
   help topics/terms in Troff markup.
 * Woman pages are generated/formatted by grosciteco at compile-time, so
   they will work on platforms without Groff (ie. as on windows).
 * Groff has been added as a hard compile-time requirement.
 * The sciteco(1) and sciteco(7) man pages have been augmented with
   help topic anchors.
</pre>
</div>
</content>
</entry>
</feed>
