G. Milde wrote:
They are not wrong but in a different encoding: witht the default
settings, this is most probably the T1 encoding where ligatures are on
places totally unrelated to the unicode points. (or even 0T1, where
Umlauts will be wrong as well).
Well, I would expect that the PDF reader
On 30.05.08, Jürgen Spitzmüller wrote:
G. Milde wrote:
They are not wrong but in a different encoding: witht the default
settings, this is most probably the T1 encoding where ligatures are on
places totally unrelated to the unicode points. (or even 0T1, where
Umlauts will be wrong as
G. Milde wrote:
Actually, on my Debian system, the xpdf reader actually de-composes an ff
ligature in a sample document and puts the two letters f+f in the
selection instead -- i.e. it works as I would expect.
Actually, it depends on the font.
* When using the default cm font, copying does
Rich Shepard wrote:
On Tue, 27 May 2008, David Hewitt wrote:
I get the same. If I try to copy from a PDF made with pdflatex, all the
ligatures show up as special characters and must be replaced. This is
with Computer Modern Roman font and standard classes (article, report).
This is to
G. Milde wrote:
On 28.05.08, Juergen Spitzmueller wrote:
The problem is that the copied characters are apparently wrong. The
clipboard should have the correct unicode code points for the ligatures,
but it has some completely different (and unrelated) chars.
They are not wrong but in a
G. Milde wrote:
They are not wrong but in a different encoding: witht the default
settings, this is most probably the T1 encoding where ligatures are on
places totally unrelated to the unicode points. (or even 0T1, where
Umlauts will be wrong as well).
Well, I would expect that the PDF reader
On 30.05.08, Jürgen Spitzmüller wrote:
G. Milde wrote:
They are not wrong but in a different encoding: witht the default
settings, this is most probably the T1 encoding where ligatures are on
places totally unrelated to the unicode points. (or even 0T1, where
Umlauts will be wrong as
G. Milde wrote:
Actually, on my Debian system, the xpdf reader actually de-composes an ff
ligature in a sample document and puts the two letters f+f in the
selection instead -- i.e. it works as I would expect.
Actually, it depends on the font.
* When using the default cm font, copying does
Rich Shepard wrote:
On Tue, 27 May 2008, David Hewitt wrote:
I get the same. If I try to copy from a PDF made with pdflatex, all the
ligatures show up as special characters and must be replaced. This is
with Computer Modern Roman font and standard classes (article, report).
This is to
G. Milde wrote:
On 28.05.08, Juergen Spitzmueller wrote:
The problem is that the copied characters are apparently wrong. The
clipboard should have the correct unicode code points for the ligatures,
but it has some completely different (and unrelated) chars.
They are not wrong but in a
G. Milde wrote:
> They are not "wrong" but in a different encoding: witht the default
> settings, this is most probably the T1 encoding where ligatures are on
> places totally unrelated to the unicode points. (or even 0T1, where
> Umlauts will be "wrong" as well).
Well, I would expect that the
On 30.05.08, Jürgen Spitzmüller wrote:
> G. Milde wrote:
> > They are not "wrong" but in a different encoding: witht the default
> > settings, this is most probably the T1 encoding where ligatures are on
> > places totally unrelated to the unicode points. (or even 0T1, where
> > Umlauts will be
G. Milde wrote:
> Actually, on my Debian system, the xpdf reader actually de-composes an ff
> ligature in a sample document and puts the two letters f+f in the
> selection instead -- i.e. it works as I would expect.
Actually, it depends on the font.
* When using the default cm font, copying does
Rich Shepard wrote:
> On Tue, 27 May 2008, David Hewitt wrote:
>
>> I get the same. If I try to copy from a PDF made with pdflatex, all the
>> ligatures show up as special characters and must be replaced. This is
>> with Computer Modern Roman font and standard classes (article, report).
>
>
G. Milde wrote:
> On 28.05.08, Juergen Spitzmueller wrote:
>
>> The problem is that the copied characters are apparently wrong. The
>> clipboard should have the correct unicode code points for the ligatures,
>> but it has some completely different (and unrelated) chars.
>
> They are not "wrong"
Rich Shepard wrote:
This is to be expected. It's perfectly normal behavior. What should be the
behavior if you block text in a pdf document (displayed with xpdf,
acroread, or another viewer) and copy that text into emacs, pine, or
AbiWord? The first two are text-mode applications, the last is
On 28.05.08, Juergen Spitzmueller wrote:
Rich Shepard wrote:
This is to be expected. It's perfectly normal behavior. What should be the
behavior if you block text in a pdf document (displayed with xpdf,
acroread, or another viewer) and copy that text into emacs, pine, or
AbiWord? The
On Wed, 28 May 2008, Juergen Spitzmueller wrote:
The problem is that the copied characters are apparently wrong. The
clipboard should have the correct unicode code points for the ligatures,
but it has some completely different (and unrelated) chars.
Jürgen,
Oh. OK. Now I understand.
Rich Shepard wrote:
This is to be expected. It's perfectly normal behavior. What should be the
behavior if you block text in a pdf document (displayed with xpdf,
acroread, or another viewer) and copy that text into emacs, pine, or
AbiWord? The first two are text-mode applications, the last is
On 28.05.08, Juergen Spitzmueller wrote:
Rich Shepard wrote:
This is to be expected. It's perfectly normal behavior. What should be the
behavior if you block text in a pdf document (displayed with xpdf,
acroread, or another viewer) and copy that text into emacs, pine, or
AbiWord? The
On Wed, 28 May 2008, Juergen Spitzmueller wrote:
The problem is that the copied characters are apparently wrong. The
clipboard should have the correct unicode code points for the ligatures,
but it has some completely different (and unrelated) chars.
Jürgen,
Oh. OK. Now I understand.
Rich Shepard wrote:
> This is to be expected. It's perfectly normal behavior. What should be the
> behavior if you block text in a pdf document (displayed with xpdf,
> acroread, or another viewer) and copy that text into emacs, pine, or
> AbiWord? The first two are text-mode applications, the
On 28.05.08, Juergen Spitzmueller wrote:
> Rich Shepard wrote:
> > This is to be expected. It's perfectly normal behavior. What should be the
> > behavior if you block text in a pdf document (displayed with xpdf,
> > acroread, or another viewer) and copy that text into emacs, pine, or
> >
On Wed, 28 May 2008, Juergen Spitzmueller wrote:
The problem is that the copied characters are apparently wrong. The
clipboard should have the correct unicode code points for the ligatures,
but it has some completely different (and unrelated) chars.
Jürgen,
Oh. OK. Now I understand.
Actually, it looks like a problem outside of LyX. Both in Acroread and
KPDF,
if if copy the ff-ligature, it doesn't put the ligature into the
clipboard,
but rather the unicode character 0x001b (ESCAPE).
I get the same. If I try to copy from a PDF made with pdflatex, all the
ligatures
On Tue, 27 May 2008, David Hewitt wrote:
I get the same. If I try to copy from a PDF made with pdflatex, all the
ligatures show up as special characters and must be replaced. This is with
Computer Modern Roman font and standard classes (article, report).
This is to be expected. It's
Actually, it looks like a problem outside of LyX. Both in Acroread and
KPDF,
if if copy the ff-ligature, it doesn't put the ligature into the
clipboard,
but rather the unicode character 0x001b (ESCAPE).
I get the same. If I try to copy from a PDF made with pdflatex, all the
ligatures
On Tue, 27 May 2008, David Hewitt wrote:
I get the same. If I try to copy from a PDF made with pdflatex, all the
ligatures show up as special characters and must be replaced. This is with
Computer Modern Roman font and standard classes (article, report).
This is to be expected. It's
> Actually, it looks like a problem outside of LyX. Both in Acroread and
> KPDF,
> if if copy the ff-ligature, it doesn't put the ligature into the
> clipboard,
> but rather the unicode character 0x001b (ESCAPE).
>
I get the same. If I try to copy from a PDF made with pdflatex, all the
On Tue, 27 May 2008, David Hewitt wrote:
I get the same. If I try to copy from a PDF made with pdflatex, all the
ligatures show up as special characters and must be replaced. This is with
Computer Modern Roman font and standard classes (article, report).
This is to be expected. It's
30 matches
Mail list logo
