Bug 83973 - FORMATTING: Makes some words/lines bold randomely when bilingual text is converted to media wiki or microsoft doc format
Summary: FORMATTING: Makes some words/lines bold randomely when bilingual text is conv...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 08:48 UTC by Mohiniraj Sutavani
Modified: 2015-05-06 14:23 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
An odt file created with writer is attached. Only some of the words are made bold font. The same is converted to mediaWiki by plugin. Some extra words are seen with bold tags in the txt file. (461 bytes, text/plain)
2014-09-17 08:48 UTC, Mohiniraj Sutavani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mohiniraj Sutavani 2014-09-17 08:48:21 UTC
Created attachment 106419 [details]
An odt file created with writer is attached. Only some of the words are made bold font. The same is converted to mediaWiki by plugin. Some extra words are seen with bold tags in the txt file.

Bilingual text (English and a Indic language script) with bold formated words are entered in a document.

When converting it to mediaWiki txt format, some extra words (randomly) get tokens/tags attached to them to make them bold.

Same behavior is observed when the odt file is saved as .doc file (in microsoft word format)some extra words (randomly) get tokens/tags attached to them to make them bold.

Expected behavior:
Only the words which are marked bold should have tokens around it.

Sample files are attached.

              
Operating System: All
Version: 4.2.4.2 release
Comment 1 Yousuf Philips (jay) (retired) 2014-09-29 03:05:38 UTC
Hello Mohiniraj,

Thank you for filing the bug. Unfortunately you submitted a text file and not an odt file, so i'm unable to test your bug.
Comment 2 QA Administrators 2015-04-01 14:47:18 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 3 QA Administrators 2015-05-06 14:21:39 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team