Bug 56647 - Arabic text (laam-alif) rendered differently in pointing (copying, reading) cell than in cell pointed to
Summary: Arabic text (laam-alif) rendered differently in pointing (copying, reading) c...
Status: RESOLVED DUPLICATE of bug 55844
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-01 21:17 UTC by b.patrick
Modified: 2013-04-30 12:41 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
snapshot of spreadsheet containing cells containing Arabic text with laam-'alif combination and cell pointing to it (207.64 KB, image/png)
2012-11-01 21:17 UTC, b.patrick 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description b.patrick 2012-11-01 21:17:31 UTC 
Created attachment 69402 [details]
snapshot of spreadsheet containing cells containing Arabic text with laam-'alif combination and cell pointing to it

1) Arabic laam-'alif combination rendered wrongly in cell J1739 (please refer to snapshot) in which they were typed. [Minor problem; retyping in different order and/or without copying often helps.]

2) However, the same laam-'alif combination in the cell I1739 that points to content of the previously mentioned cell J1739.

The real (but rather minor) problem clearly lies in original cell, which probably memorizes (somehow) the way and/or order in which it was filled with text.

OS:  Linux 2.6.34.10-0.6-desktop x86_64
  System:  openSUSE 11.3 (x86_64)
  KDE:  4.4.4 (KDE 4.4.4) "release 3"

Processor (CPU):   Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
  Speed:  1,596.00 MHz
  Cores:  4
Comment 1 b.patrick 2012-11-19 07:58:58 UTC 
Most of the time (or always), retyping the "laam-fatHa-'alif" sequence in one go results in the correct "laam-'alif" ligature being displayed in the original cell (as well as the one pointing to its contents).
Comment 2 b.patrick 2012-11-24 20:53:12 UTC 
This report seems to be covered completely by report 55844, and could probably be added to that report and/or discontinued.
Comment 3 Urmas 2013-04-30 12:41:44 UTC 

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