Bug #925589 “[Upstream] Libreoffice-wiki-publisher: Translation ...” : Bugs : LibreOffice

Revision history for this message

Alexander Kallenbach (kallenbachalex) wrote on 2012-02-02:

#1

Dependencies.txt Edit (3.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Alexander Kallenbach (kallenbachalex) wrote on 2012-02-02:

#2

Tabelle Beispieldokument.odt Edit (8.9 KiB, application/vnd.oasis.opendocument.text)

Revision history for this message

Alexander Kallenbach (kallenbachalex) wrote on 2012-02-02:

#3

Tabelle Beispieldokument.txt Edit (967 bytes, text/plain)

Revision history for this message

In Document Foundation Bugzilla #45960, Kallenbachalex-i (kallenbachalex-i) wrote on 2012-02-12:

#9

Created attachment 56924
exemplary document - odt version

I've generated a chart in which I merged some cells. The wiki-publisher didn't translate the merging (it should in my case add a "rowspan: "3""). I'll attach an exemplary document.

I've already posted a bugreport on Launchpad:

https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/925589

Revision history for this message

In Document Foundation Bugzilla #45960, Kallenbachalex-i (kallenbachalex-i) wrote on 2012-02-12:

#10

Created attachment 56925
exemplary document - txt version

Revision history for this message

In freedesktop.org Bugzilla #45960, Alexander Kallenbach (kallenbachalex) wrote on 2012-02-12:

#4

Created attachment 56924
exemplary document - odt version

I've generated a chart in which I merged some cells. The wiki-publisher didn't translate the merging (it should in my case add a "rowspan: "3""). I'll attach an exemplary document.

I've already posted a bugreport on Launchpad:

https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/925589

Revision history for this message

In freedesktop.org Bugzilla #45960, Alexander Kallenbach (kallenbachalex) wrote on 2012-02-12:

#5

Created attachment 56925
exemplary document - txt version

Bug Watch Updater (bug-watch-updater) on 2012-02-12

Changed in df-libreoffice:
importance:	Unknown → Medium
status:	Unknown → New

penalvch (penalvch) on 2012-02-12

summary:

- Libreoffice-wiki-publisher: Translation of charts into wikitext is
- incorrect
+ [Upstream] Libreoffice-wiki-publisher: Translation of charts into
+ wikitext is incorrect

Revision history for this message

In freedesktop.org Bugzilla #45960, thackert (thackert) wrote on 2012-09-29:

#6

Hello Alexander, *,
I can confirm this issue with LO Version 3.6.2.2 (Build ID: da8c1e6) under Debian Testing x86. If you enter the text of the exported wiki text in a wiki itself (I have tested it in my user profile at wiki.documentfoundation org), the right borders of rows 2 and 3 have no border on their right ... :(
HTH
Thomas.

Revision history for this message

In Document Foundation Bugzilla #45960, thackert (thackert) wrote on 2012-09-29:

#11

Hello Alexander, *,
I can confirm this issue with LO Version 3.6.2.2 (Build ID: da8c1e6) under Debian Testing x86. If you enter the text of the exported wiki text in a wiki itself (I have tested it in my user profile at wiki.documentfoundation org), the right borders of rows 2 and 3 have no border on their right ... :(
HTH
Thomas.

Bug Watch Updater (bug-watch-updater) on 2012-10-04

Changed in df-libreoffice:
status:	New → Confirmed

Revision history for this message

In freedesktop.org Bugzilla #45960, Qa-admin-q (qa-admin-q) wrote on 2015-01-05:

#7

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team

Revision history for this message

In Document Foundation Bugzilla #45960, Qa-admin-q (qa-admin-q) wrote on 2015-01-05:

#12

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team

Revision history for this message

In Document Foundation Bugzilla #45960, Beluga (beluga) wrote on 2015-01-28:

#13

Still the same result.

Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+
Build ID: 784d069cc1d9f1d6e6a4e543a278376ab483d1eb
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-25_23:07:36

Revision history for this message

In Document Foundation Bugzilla #45960, Qa-admin-q (qa-admin-q) wrote on 2016-02-21:

#14

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice
(5.0.5 or 5.1.0) https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   Update the version field
   Reply via email (please reply directly on the bug tracker)
   Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
   appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice 
   (5.0.5 or 5.1.0)  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and 
   your operating system, and any changes you see in the bug behavior
 
   If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
   a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
   Reply via email (please reply directly on the bug tracker)
   Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
   appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21

Revision history for this message

In Document Foundation Bugzilla #45960, Qa-admin-q (qa-admin-q) wrote on 2017-03-06:

#15

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice
(5.2.5 or 5.3.0 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170306

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice 
(5.2.5 or 5.3.0  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and 
your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170306

Revision history for this message

Marcus Tomlinson (marcustomlinson) wrote on 2019-08-13:

#8

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in libreoffice (Ubuntu):
status:	New → Incomplete

Marcus Tomlinson (marcustomlinson) on 2019-08-13

Changed in df-libreoffice:
importance:	Medium → Unknown
status:	Confirmed → Unknown

Bug Watch Updater (bug-watch-updater) on 2019-09-02

Changed in df-libreoffice:
importance:	Unknown → Medium
status:	Unknown → Confirmed

Revision history for this message

Marcus Tomlinson (marcustomlinson) wrote on 2019-09-25:

#16

Synchronising bug status with upstream.

Changed in libreoffice (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

In Document Foundation Bugzilla #45960, Qa-admin-q (qa-admin-q) wrote on 2019-12-03:

#17

Dear Alexander Kallenbach,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

Revision history for this message

In Document Foundation Bugzilla #45960, Qa-admin-q (qa-admin-q) wrote on 2021-12-03:

#18

Dear Alexander Kallenbach,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

Affects		Status	Importance	Assigned to	Milestone
	LibreOffice	Confirmed	Medium	tdf #45960
	libreoffice (Ubuntu)	Confirmed	Undecided	Unassigned

LibreOffice

[Upstream] Libreoffice-wiki-publisher: Translation of charts into wikitext is incorrect

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches