Mailinglist Archive: opensuse-bugs (10798 mails)

< Previous Next >
[Bug 547973] New: After save a Calc file with Cyrillic text (Bulgarian, Russian etc. …) get all the letters replaced by '?'.
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 18 Oct 2009 01:36:48 -0600
  • Message-id: <bug-547973-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: After save a Calc file with Cyrillic text (Bulgarian,
Russian etc. …) get all the letters replaced by '?'.
Classification: openSUSE
Product: openSUSE 11.2
Version: RC 1
Platform: i686
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
AssignedTo: bnc-team-ooo@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: kiv@xxxxxxxxxxxxxxx
QAContact: kyu@xxxxxxxxxx
Found By: ---

Created an attachment (id=322986)
--> (
Example file to open and then save in order to see what happens

User-Agent: Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.1
(like Gecko) SUSE

When create or open a Calc file written with UTF8 Cyrillic text (Bulgarian,
Russian etc. …) and save it (xls or OpenDucument) the letters in the text will
be replaced by question marks.
Next time when you open the file you will have all leters in your text like
‘?’. This makes such files totaly unusable.
I can not found a way to convert back the question marks to normal text.
This way from openSuSE 11.2 up to RC 1 is destroying the users
data where Save operation is used.
Same operation with 3.3.3 (OOO310m19 (Build 3420)) by SUN works
I believe this bug is top rpiority and show stopper for openSuSE 11.2 (at
least for the customers who use Cyrillic text)

Reproducible: Always

Steps to Reproduce:
1.Open the attached example file
2.Try to make some corrections or do not any thing
3.Save a copy of it
4.Open it again anc open the copy
5.See the difference between the original and saved copy of it
Actual Results:
All Cyrillc letters get replaced by question marks '?'

Expected Results:
To see the Cyrillic text same as when open before the Save operation.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >