Bug 69310 - EDITING: Hindi/Devanagari Fonts incorrect rendering while editing (CDAC, Nithyananda, Gurumaa, sadhguru, etc. hindi fonts)
Summary: EDITING: Hindi/Devanagari Fonts incorrect rendering while editing (CDAC, Nith...
Status: RESOLVED DUPLICATE of bug 70968
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.1.1 rc
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-09-13 09:53 UTC by Asif Ali Rizvan
Modified: 2013-10-31 10:36 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screenshot with different devanagari/hindi fonts in libreoffice writer 4.1.2.1 on fedora 20 (190.85 KB, image/png)
2013-09-13 09:53 UTC, Asif Ali Rizvan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Asif Ali Rizvan 2013-09-13 09:53:50 UTC
Created attachment 85757 [details]
screenshot with different devanagari/hindi fonts in libreoffice writer 4.1.2.1 on fedora 20

Problem description: 
Some devanagari (complex text layout) fonts are not rendered properly, especially while editing. 

But when loading the saved file shows the text properly, but again text gets garbled up when we try to edit.

Steps to reproduce:
1. install CDAC fonts from: http://biharvidhanparishad.gov.in/HindiFonts.htm
or Nithyananda font from: http://gnome-look.org/content/show.php?content=142684 

2. paste this text in writer "किंचित कहीं ऐसा होता है जिसमें फॉन्ट ठीक से रेन्डर न करे."
3. apply the font say 'nithyananda', the text looks fine, but as soon as we try to change/add anything like space the text layout gets messed up.

Current behavior:
Devanagari fonts while editing are rendered incorrectly

Expected behavior:
Like libreoffice 3.x series, the text should render properly.
              
Operating System: Fedora
Version: 4.1.1.1 rc
Comment 1 ⁨خالد حسني⁩ 2013-10-30 17:58:16 UTC

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