Apache OpenOffice (AOO) Bugzilla – Issue 74052
Importing or exporting Word (DOC) documents in Hebrew
Last modified: 2013-08-07 14:38:26 UTC
When importing or exporting Word documents with bullets or numbering in Hebrew (right to left document) language the forma of the bullets is lost ... intead of showing indentating level they are all appearing at one level ... like : In Open Office: 1. xxxxx 1.1 xxxxxx 1.1.1 xxxxx ... In Word (DOC format): 1. xxxxx 1.1 xxxxx 1.1.1 xxxx ... this happend when saving or importing in Hebrew DOC format - right to left ... if you do the same action in RTF format everything is fine ... This bug is already years old and it prevent of using OpenOffice in Hebrew ! Thanks Samuel
samia, please attach sample document. (Priority is reduced).
MRU->HBRINKM: when exporting numbered paragraphs, the indentation of the sublevels are lost when exporting to Word format. No attacment needed, just enter a numbering as described in RTL context.
First of all this happen also when importing from Word and it apply to bullets and numbers. Second ... do you have a target date for this fix ? Its the most severe priority ... Thanks
Please read the OOo pages about "Quality Assurance - Issue Handling" accessible via http://qa.openoffice.org/ooQAReloaded/ooQA-IssueRules.html before changing any Priorities. We cannot give an exact point of time where this issue could be fixed; this is represented by the target "office later". Because there are many other issues which are much more important (crashes, loops and so on...) we have to keep this time line. As far as anyone in the community could contribute a patch proposal for this issue, it will be handled with much higher priority. But as long as this is not the case, the development of SUN will follow it own rules and priorities. Thanks for your patience.
I understand what you say but I can assure you that this bug is more critical then crashes - at least here. Crashes happen also in Microsoft Office ... so people are used to it ... nothing new ... but when someone (like a big corporate ...) try to adopt OOo instead of MS Office and import its first file (or export it) to Word and see the bullets and number results ... this is the end of the product. Every bug in a local language - and I am not speaking about minor ones that will always exist - is crucial and basically stop the product penetration. Again ... this is your decision ... but till then no one here will work with the product ... and the current situation just prove my point ... the penetration in a high-tech country like Israel of OOo is almost zero ... and belive me its not because people love MS ... :-) ... PS. Just FYI ... I am a developer and executive that worked for Lotus, Borland, IBM, Sun Microsystems and ... many years for Microsoft basically being one of the leaders of MS Office, Windows and other products ... and I can just say that OOo is basically a great product (I know him fro the Star Office days ...) but no one in your organization have the knowledge, experience or "know-how" to market a product like this and to "put the finger" on the right development points that make the difference ... this is so frustrating ... Till then ... when someone will be ready to invest and give experienced people that did it before (like me ...) to handle those issues in a professional way ... MS can "sleep well" and make every year more then $12 billions from office alone with a 87% net profit ... :-) ... Bye
samia, may I suggest the following course of action - get people vote for the problem. Find online community, get yourself involved and pollitely ask people to vote for this issue. Ask your friends, collegues, relatives etc vote for it (just make sure everybody plays fairly - one registration in IssueTracker per household). Since you are developer you may even try developing patch yourself or sponsor developer to do this for you, or something like that.
I am writing directly to all of you as the issue became so severe and critical. I reported a few times (see also bellow) about a critical bug In Open Office writing from right to left (Hebrew) ... when using bullets or numbering and exporting to WORD or saving in Word format all sublevels and levels are lost the all formatting are also lost. Today I installed the new version 2.2 ... and its a disaster ... even when opening the DOC format in open Office itself again ruin all the formatting and sublevels ... not only when opened in MS WORD. Basically instead of fixing the situation you make it worst and totally impossible to work with this software in Hebrew even without any concerns to WORD !!! How could something like that happen ? Is some one going to fix this issue ASAP - at least as it was before or is the Hebrew market totally doesn't interest anyone there ? For years I am amazed that in a high-tech country like Israel which such a potential use of Office tools (MS sell about $60,000,000 in Israel of Office SW alone yearly ... you can calculate how many copies it means ...) ... and with almost all the important companies in the world having developments center and subsidiaries - and I am not even mentioning speaking about Israeli companies like AMDOCS, COMVERSE, NICE ... and many others - your organization doesn't even try to solve such a critical problem that could change the market. A few years ago all Israeli government agencies , ministries and army forces were ready to throw MS Office out and adopt Open Office ... the English product was great but when they tried the Hebrew version they returned immediately to sign a contract with MS ... The Hebrew version look like a VERY bad joke ! Why are you releasing a Hebrew version at all in such a situation and status ... so buggy and unprofessional ... that cause only damage to your product and organization image here and eventually worldwide through the numerous international companies that work and develop here ... It would be better if you wouldn't release it at all in its former and especially current situation where it make a joke from Sun Microsystems and your organization locally ! What a miss ... but apparently no one really care ! Please let me know your answer. Thanks Samuel
duplicate *** This issue has been marked as a duplicate of 58982 ***
close the duplicate
So is it solved in version 3.0 ?