diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely
index 5a7a93f..9797ca6 100644
--- a/Documentation/user/advanced-notation.itely
+++ b/Documentation/user/advanced-notation.itely
@@ -581,9 +581,8 @@ Init files: @file{scm/@/new@/-markup@/.scm}.
 
 @refbugs
 
-Kerning or generation of ligatures is only done when the @TeX{}
-backend is used.  In this case, LilyPond does not account for them so
-texts will be spaced slightly too wide.
address@hidden the TeX backend is no longer implemented,
address@hidden so any mention has to be removed... -vv
 
 Syntax errors for markup mode are confusing.
 
diff --git a/scm/define-markup-commands.scm b/scm/define-markup-commands.scm
index 5405aff..2ece185 100644
--- a/scm/define-markup-commands.scm
+++ b/scm/define-markup-commands.scm
@@ -225,29 +225,11 @@ normally inserted before elements on a line."
 
 (define-builtin-markup-command (postscript layout props str) (string?)
   "This inserts @var{str} directly into the output as a PostScript
-command string.  Due to technicalities of the output backends,
-different scales should be used for the @TeX{} and PostScript backend,
-selected with @code{-f}. 
+command string. 
 
-For the @TeX{} backend, the following string prints a rotated text
-
address@hidden rotated text
-
address@hidden
-0 0 moveto /ecrm10 findfont 
-1.75 scalefont setfont 90 rotate (hello) show
address@hidden example
-
address@hidden
-The magical constant 1.75 scales from LilyPond units (staff spaces) to
address@hidden dimensions.
-
-For the postscript backend, use the following
 
 @example
-gsave /ecrm10 findfont 
- 10.0 output-scale div 
- scalefont setfont 90 rotate (hello) show grestore 
+ a-\markup { \postscript #"2 6 moveto 1 6 1  0 180 arc 0.2 setlinewidth stroke"}
 @end example"
 
   ;; FIXME