> 2010/1/4 Minh Duc Thai <thmduc@gmail.com>:
> > Hello Chris,
> > I've attached example files and my .vimrc configuration file. Hope you or
> > someone can help.
> > Thank you!
>
> I tested using your example, and can confirm that Print does not work
> well on Windows when enc=utf-8. I tried enc=latin1 and enc=cp936, and
> in both cases Print is successful (as long as the characters can be
> displayed in that encoding).
>
> I tested using the Adobe PDF driver.
On debian stable, I also tested printing utf-8 encoded files containing
samples of CJK, Devanagari, and a couple other Eastern scripts and I was
unable to get :hardcopy to print their contents.
Since utf-8 is the default encoding on debian Lenny, I find it hard to
believe that the Vim to Postscript implementation would not function out
of the box with utf-8 encoded files, and even less plausible that I was
unable to find anyone reporting this issue while searching online, apart
from a few reports where Vim 7.0 or older was involved, and dating back
7-8 years ago.
Leads me to think that there's more to it than the speculations in my
earlier post today.
Note, that I tried to implement the following in my .vimrc, also without
success:
| set printexpr=PrintFile(v:fname_in)
| function PrintFile(fname)
| call system('paps --font="unifont 8" --paper letter | lpr ' . a:fname)
| call delete(a:fname)
| return v:shell_error
The characters from the 'exotic' scripts were replaced by inverted
question marks or blanks, and _as far as I can tell_ it looked as if the
same ASCII or latin1 font was used not matter what font I passed to the
paps converter.
Can anyone shed some light on this mattter?
Thanks,
CJ
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment