Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1229848

Summary: The text name for the components get distorted in exported PDF or PNG in BPM Suite 6.1
Product: [Retired] JBoss BPMS Platform 6 Reporter: Amana <ajuricic>
Component: jBPM DesignerAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED DUPLICATE QA Contact: Kirill Gaevskii <kgaevski>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: alazarot
Target Milestone: ---   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1229853 (view as bug list) Environment:
Last Closed: 2015-06-09 19:19:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1229853    
Attachments:
Description Flags
process_pdf_png
none
samplePDF
none
samplePNG none

Description Amana 2015-06-09 19:01:15 UTC
Description of problem:

The text name for the components get distorted in exported PDF or PNG in BPM Suite 6.1. It happens when the text name is split in two lines.

The attached images show that before exporting the text name is OK. In PDF/PNG it shows distorted. Sometimes it is even out the component.

Version-Release number of selected component (if applicable):

BPM Suite 6.1

How reproducible:

Using text names split in two lines.

Steps to Reproduce:
1.
2.
3.

Actual results:

Text names distorted in pdf / png.

Expected results:

It should be aligned.

Additional info:

Comment 1 Amana 2015-06-09 19:01:44 UTC
Created attachment 1036928 [details]
process_pdf_png

Comment 2 Amana 2015-06-09 19:03:20 UTC
Created attachment 1036929 [details]
samplePDF

Comment 3 Amana 2015-06-09 19:03:46 UTC
Created attachment 1036930 [details]
samplePNG

Comment 5 Amana 2015-06-09 19:19:34 UTC

*** This bug has been marked as a duplicate of bug 1216247 ***