npak(a)ispras.ru (Nick V. Pakoulin) writes:
> NVP> contains changes to ps-mule that I made to enable printing in russian.
This looks promising..
> --- - Thu Nov 30 16:27:49 2000
> +++ lisp/ps-print/ps-mule.el Thu Nov 30 15:12:55 2000
> ＠＠ -143,8 +143,9 ＠＠
> ;; For Emacs 20.2 and the earlier version.
> - (if (and (boundp 'mule-version) ; only if mule package is loaded
> - (not (string< mule-version "4.0")))
> +;; (if (and (boundp 'mule-version) ; only if mule package is loaded
> +;; (not (string< mule-version "4.0")))
> + (if (featurep 'mule)
> (defalias 'ps-mule-next-point '1+)
> (defalias 'ps-mule-chars-in-string 'length)
This was to be expected
[What was the exact problem here (I don't have a mule-build handy). Is
"mule-version" not defined on our mule build does it not have the
> +;;; The following commented code does not compile under XEmacs 21.2.36
> +;;; npak(a)ispras.ru
> [ Ethiopic support comment out]
Ok, we simply have no Ethoipic support
> ;; A charset which we are now processing.
> (defvar ps-mule-current-charset nil)
> ＠＠ -934,6 +939,10 ＠＠
> (cond ((coding-system-p encoding)
> (encode-coding-string str encoding))
> + ;; XEmacs change npak(a)ispras.ru
> + ((and (symbolp encoding)
> + (find-coding-system encoding))
> + (encode-coding-string str (find-coding-system encoding)))
> ((functionp encoding)
> (funcall encoding str))
Hmm.. Do we have a slight API incompatibility here, i.e. can we not
take a coding system name in encode-coding-string?
Anyway, it just another minor problem.
> (and (boundp 'enable-multibyte-characters)
> - enable-multibyte-characters
> + ;; FIXME
> + ;;enable-multibyte-characters
I think is again just a misguided FSF-specific mule test
> [From another message:]
> (define-coding-system-alias 'cyrillic-iso-8bit 'iso-8859-5)
I think was the essential bit... FSF Emacs has a whole bunch of
different names for coding systems.
I think the core bits work.
Could you, just for laughs, try printing using the bdf fonts if
you have the intlfont package installed.