Issue 1925 - CJK sheet name not allowed
Summary: CJK sheet name not allowed
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: 638
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: peter.junge
QA Contact: issues@sc
URL:
Keywords:
: 3715 4984 4985 5186 6488 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-10-17 07:48 UTC by Unknown
Modified: 2003-09-08 16:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2001-10-17 07:48:07 UTC
In SPREADSHEET, if user rename the sheet and enter a CJK string as the sheet 
name, OOo would pop up the message "Invalid sheet name". 

The source code shows that ScDocument::ValidTabName() in sc module, which in 
turn calls CharacterClassification::parseText() in i18n module, returns FALSE 
when the sheet name is CJK. Thus I suggest this problem may relates to the i18n 
UNO network. Please fix this issue or provide further info on how to plug CJK 
locale to the i18n UNO network.
Comment 1 oc 2001-10-17 10:23:27 UTC
This is something for I18N
Comment 2 ooo 2001-10-18 15:10:36 UTC
Will be functional when the new i18n framework is ready, see
http://l10n.openoffice.org/i18n_framework/Open-sourcing_i18n_framework.html
Comment 3 peter.junge 2002-04-03 12:53:33 UTC
*** Issue 3715 has been marked as a duplicate of this issue. ***
Comment 4 ooo 2002-05-13 16:16:26 UTC
With the new i18npool/source/characterclassification/* replacing the
old i18n/source/characterclassification/* in the next 642 build this
should be resolved.
Comment 5 csoh 2002-05-17 07:32:55 UTC
Problem still exists for 1.0.0 win32 korean localized build.
In addition, when user imports Excel spreadsheet with korean sheet 
name(s), all of the name changes to underbar('_') of equal byte 
lengths.
Comment 6 ooo 2002-05-17 08:56:56 UTC
er->csoh: as I said, the fix will be in the next 642 build. It will
not be available in the 641 line on which OOo1.0 is built.
Comment 7 oc 2002-05-21 15:09:56 UTC
*** Issue 4984 has been marked as a duplicate of this issue. ***
Comment 8 oc 2002-05-21 15:10:19 UTC
*** Issue 4985 has been marked as a duplicate of this issue. ***
Comment 9 ooo 2002-08-09 14:19:00 UTC
*** Issue 6488 has been marked as a duplicate of this issue. ***
Comment 10 peter.junge 2002-09-25 13:18:20 UTC
*** Issue 5186 has been marked as a duplicate of this issue. ***
Comment 11 ooo 2002-12-09 15:43:58 UTC
Have to reopen to reassign, rediculous.
Comment 12 ooo 2002-12-09 15:44:54 UTC
reassign to QA
Comment 13 ooo 2002-12-09 15:46:00 UTC
restore status
Comment 14 peter.junge 2003-02-10 17:45:56 UTC
No Problem in latest version from 644 trunk -> verified
Comment 15 peter.junge 2003-02-10 17:46:13 UTC
-> clsoed