Issue 93601 - Default title for table of contents should reside in the locale data, not UI localization
Summary: Default title for table of contents should reside in the locale data, not UI ...
Alias: None
Product: Internationalization
Classification: Code
Component: localedata (show other issues)
Version: OOo 2.4.1
Hardware: All All
: P4 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Blocks: 41707 92549
  Show dependency tree
Reported: 2008-09-08 11:39 UTC by tantai
Modified: 2013-01-29 21:42 UTC (History)
4 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description tantai 2008-09-08 11:39:17 UTC
Steps to reproduce:

1. Open Writer
2. Insert -> Indexes and Tables -> Indexes and Tables...
3. In Index/Table Tab in the Title box, the default text is "Table of Contents"

The default text in Title box should depend on locale so localizers can
translate the word.
Comment 1 ooo 2008-09-08 12:54:50 UTC
Nothing to do with locale data.
@sba: The initial content of the edit field depends on the UI localization, if
I'm not mistaken. To be confirmed.
Comment 2 samphan 2008-09-11 03:24:13 UTC
I've tested to confirm that the "Indexes and Tables" string is in UI 
localization. And it is. When I choose Thai as the UI language and the text will 
be 'สารบัญ'.

However, most Thai use en-US UI so they will have to re-type the text every 
time. Logically, the locale setting specify the preference for "the language of 
the document", right? While the UI setting specify the preference for the 
current user in front of the PC. Shouldn't the best guess for the string come 
from locale?

The point of this issue is that the string like "Table of Contents" should be 
moved from UI localizaton to locale data.
Comment 3 jarl 2011-04-29 08:00:40 UTC
I confirm this bug.

My UI is danish, and I often write english documents.
Comment 4 jarl 2011-04-29 08:12:45 UTC
I suggest this is being marked a duplicate of bug#117522, as the problem is in the "Word processor". and states the problem rather than a proposed solution in the summary.