Bug 1029 - Libreoffice fails to edit TOC in breton
Summary: Libreoffice fails to edit TOC in breton
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: D Morgan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-28 15:02 CEST by Thierry Vignaud
Modified: 2011-04-29 13:26 CEST (History)
1 user (show)

See Also:
Source RPM: libreoffice
CVE:
Status comment:


Attachments
error dialog (9.84 KB, image/png)
2011-04-28 15:07 CEST, Thierry Vignaud
Details

Description Thierry Vignaud 2011-04-28 15:02:21 CEST
Description of problem:
There's a bug in librenoffice when running in the br_FR locale.
It fails to edit TOC (Table of Content)

The issue is that %_libdir/libreoffice/basis3.3/share/template/br/ is empty.
So I suggest we symlink
/usr/lib64/libreoffice/basis3.3/share/template/br/ on
/usr/lib64/libreoffice/basis3.3/share/template/fr/
(and adding a require from lo-br to lo-fr)

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


How reproducible:


Steps to Reproduce:
1. run lo in breton (l=br_FR.UTF-8;LANG=$l LC_ALL=$l LC_MESSAGES=$l oowriter)
2. insert a Table Of Contents
3. Right click on it and try to edit it
Comment 1 Thierry Vignaud 2011-04-28 15:07:03 CEST
Created attachment 314 [details]
error dialog

Which means

"internal/idxeample.sdw" cannot be found in file:///usr/lib64/libreoffice/basis3.3/share/template/br;vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/templates;(...)

Indeed /usr/lib64/libreoffice/basis3.3/share/template/br is empty whereas /usr/lib64/libreoffice/basis3.3/share/template/fr is not

Symlinking the former on the later fixes it
D Morgan 2011-04-28 15:30:48 CEST

CC: (none) => dmorganec
Assignee: bugsquad => dmorganec

Frédéric "LpSolit" Buclin 2011-04-28 23:12:17 CEST

Summary: librenoffice fails to edit TOC in breton => Libreoffice fails to edit TOC in breton

Comment 2 D Morgan 2011-04-29 13:26:29 CEST
i just fixed on svn, thanks for this report thierry.

Please reopen if not working with next release.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.