[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #1 from Adam CloudOn --- Created attachment 78874 --> https://bugs.freedesktop.org/attachment.cgi?id=78874&action=edit LibreOffice Font Bug - Screenshot -- You are receiving this mail because: You are the assignee for the bug. ___

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 Jorendc changed: What|Removed |Added CC||jmadero@gmail.com, |

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #3 from Joel Madero --- the file is not corrupt - Microsoft Office only supports an older version of open standards (ODF), so when you try to save with the new standards which is default for LibreOffice it doesn't know what to do and

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #4 from Adam CloudOn --- Maybe I was misunderstood or maybe I didn't understand @Joel's comment.. I did not mean saving DOCX as ODF and trying to open it in MS Word. I meant working only with DOCX files. Open DOCX in LO - save it as

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #5 from Joel Madero --- indeed this would be a much more serious problem, I misunderstood, will attempt to test today -- You are receiving this mail because: You are the assignee for the bug.

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 Joel Madero changed: What|Removed |Added Status|UNCONFIRMED |NEW CC|

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 Joel Madero changed: What|Removed |Added Hardware|Other |All OS|Windows (All)

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #7 from Gerry --- @Adam: Is it possible that your original file has a formatting error? Opening your test docx-file in Word 2010 I see that the font name is "Times New Roman (Headings CS)" I do not exactly know how it came in the W

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 Joel Madero changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #8 from Joel Madero

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #9 from Adam CloudOn --- I have investigated what happens here, and this is what I *think* happens: The DOCX file I have attached has a tag called : this tag means 'run fonts', and what I understand from investigation is that it d

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-05-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 Joel Madero changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this mail becaus

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-07-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #10 from Shai Petel --- I can confirm this happens to me with Office 2013, and I think I know why and what was changed. Hope this can help: I cracked open the docx file and noticed this behaviour, text using any one of the theme font

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-07-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #11 from Shai Petel --- Created attachment 82600 --> https://bugs.freedesktop.org/attachment.cgi?id=82600&action=edit File with Hebrew text example of the problem. Only one word uses a non theme font that works Note in this file ex

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-07-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 Shai Petel changed: What|Removed |Added Severity|normal |major Priority|medium

[Libreoffice-bugs] [Bug 64232] FILEOPEN: [FILEOPEN] [FORMATTING] [DATALOSS] Importing DOCX with default font 'Times New Roman' - shown as different font in Writer

2013-07-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=64232 --- Comment #12 from Adam CloudOn --- (In reply to comment #10) > I can confirm this happens to me with Office 2013, and I think I know why > and what was changed. > Hope this can help: > Your analysis looks exactly like mine, so I guess we are