Issue 87686 - Problem with accent in vertical text when exporting to PDF
Summary: Problem with accent in vertical text when exporting to PDF
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 2.4.0
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: OOo 3.x
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Blocks: 95057 97991
  Show dependency tree
Reported: 2008-04-01 10:21 UTC by becho4
Modified: 2013-07-30 02:13 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Sample writer document (7.62 KB, text/plain)
2008-04-01 10:22 UTC, becho4
no flags Details
Sample writer document exported to pdf (74.03 KB, text/plain)
2008-04-01 10:22 UTC, becho4
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description becho4 2008-04-01 10:21:25 UTC
- Create a new writer document
- Place a text drawing object
- Fill in a text with an accent, for example "Formación"
- Rotate the Text object to 90 degrees
- Export the document to pdf

The text object in resulting pdf document contains "Formaci". The word is truncated.
Comment 1 becho4 2008-04-01 10:22:17 UTC
Created attachment 52424 [details]
Sample writer document
Comment 2 becho4 2008-04-01 10:22:54 UTC
Created attachment 52425 [details]
Sample writer document exported to pdf
Comment 3 michael.ruess 2008-04-01 10:50:51 UTC
Reassigned to HI.
Comment 4 h.ilter 2008-04-01 15:54:20 UTC
Reassigned to HDU
Comment 5 Mathias_Bauer 2008-04-21 16:29:25 UTC
changed component
Comment 6 2008-06-04 13:05:35 UTC
Confirmed with DEV300_m16
Comment 7 2008-06-05 15:25:21 UTC
have to retarget (I hope to get a solution for OOo3 though)
Comment 8 2009-01-12 09:51:18 UTC
Probably related to issue 97326
Comment 9 2009-01-12 10:57:00 UTC
Not related to issue 97326.

@pl: since CWS glyphadv PdfWriter_Impl::drawLayout() has bad problems in situations with nGlyphs!=1 and 
nOrientation!=0, because the glyph iteration in this method ignores the orientation. The bug is usually hidden by 
the fact that the glyph run is merged, so the PDF text matrix does the glyph position update (correctly) instead 
of the code in drawLayout (incorrectly). The accented glyph triggers the bug becoming visible because of its 
type1-glyph advance.

The most simple workaround against this bug in PdfWriter_Impl::drawLayout() is to set nMaxGlyps=1 to let 
GetNextGlyphs() do the work of calculating the correct positions. The point of CWS glyphadv was to reduce the 
PDF size by merging glyph runs whereever possible, so this workaround is no good long term fix.
Comment 10 philipp.lohmann 2009-01-12 11:22:10 UTC
And would you perchance enlighten me with your wisdom what exactly is supposed
to be wrong in there ?
Comment 11 2009-01-12 11:51:00 UTC
> And would you perchance enlighten me with your wisdom what exactly is supposed to be wrong in 
there ?

Sure, listen to these words of wisdom:
The line
   aGNGlyphPos.X() += nAdvanceWidths[i]/rLayout.GetUnitsPerPixel();
only works when orientation==0. Likewise the line when the vertical-alternate glyphs are enabled
   aGNGlyphPos.Y() += nAdvanceWidths[i]/rLayout.GetUnitsPerPixel();
only works when orientation==2700.
The proper solution is to advance the glyph postion in the direction requested by the orientation.
Comment 12 philipp.lohmann 2009-01-12 12:01:03 UTC
and where o wise master do I get the information from that the direction changes
within a glyph run ? And why doesn't the layout deliver different orientations
in a run in the first place ? Since obviously the advancement array in such a
case does not make much conceptual sense.
Comment 13 2009-01-12 12:24:29 UTC
A layout and thus a glyph run only has one orientation. The advancement array is in the direction of that 
orientation. The individual glyph positions are thus something like
  nPixelWidthSum = nAdvWidthSum / rLayout.GetUnitsPerPixel()
  Point aPixOfs = Point( cos_oriented*nPixelWidthSum, sin_oriented*nPixelWidthSum)
  aGNGlyphPos = aBasePoint + aOrientedOffset
Since some orientations are more common than others and a glyph run often contains just one glyph there 
are some obvious optimization possibilities.

Comment 14 2009-01-12 12:27:00 UTC
Comment 15 philipp.lohmann 2009-01-12 12:31:34 UTC
Comment 16 Rob Weir 2013-07-30 02:13:19 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.