Download it now!
Bug 88600 - On converting text to table create a new row on both paragraph and line break (shift+enter)
Summary: On converting text to table create a new row on both paragraph and line break...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Tables-Enhancements
  Show dependency treegraph
 
Reported: 2015-01-19 21:17 UTC by Gabriele Ponzo
Modified: 2020-02-04 16:28 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Example of pseudo-tables with tabulations and convertions in tables (20.81 KB, application/vnd.oasis.opendocument.text)
2015-01-19 21:17 UTC, Gabriele Ponzo
Details
Proposed ena (28.92 KB, application/x-designer)
2020-02-04 12:57 UTC, Gabriele Ponzo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriele Ponzo 2015-01-19 21:17:56 UTC
Created attachment 112499 [details]
Example of pseudo-tables with tabulations and convertions in tables

I find that building pseudo-tables with tabulations is often useful and in those cases I use (and teach) to separate each row with forced Carriage Return (Shift+Enter).

This way it's not necessary to select each row of this pseudo-table, for example, to modify a tabulation. It's enough to have keyboard cursor inside that unique paragraph.

If You try to convert such a pseudo-table in a real table with the specific function, it will ignore CR and create a one row table with a number of columns that equals intended columns multiplied by intended rows.

I'm not a coder (anymore), but I guess it should be an easy feature to implement, just adding the CR code to the existing "End of Paragraph" in the parsing of the "End of Line" function. It should be about an OR operator.
Comment 1 Buovjaga 2015-01-29 18:05:58 UTC
Confirmed the current behavior and set to NEW.

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
Comment 2 Gabriele Ponzo 2020-02-04 12:57:28 UTC
Created attachment 157641 [details]
Proposed ena
Comment 3 Gabriele Ponzo 2020-02-04 13:08:42 UTC
Sorry for previous comment, I must have stumbled in some key :)
---
I've attempted to find the point to edit and follow a little bit, but I'm not a dev.

The attachment is a proposal for the UI Dialog enhancement, but I didn't check it against UX/UI directives.

So I' hope all this stuff may help a good willing soul to commit this little enhancement.

The piece of code involved (first) should be this one:
https://opengrok.libreoffice.org/xref/core/sw/source/ui/table/convert.cxx

But I'm not able to edit it in order to add such a feature.
I believe I've already gone far beyond my skill here, thanks to after FOSDEM's HackFest and obviously to Micheal Meeks and Kendy :)
Comment 4 Heiko Tietze 2020-02-04 14:57:37 UTC
Why not just take the line breaks as normal breaks when converting the text. Is it so crucial to keep 1<BR>2<TAB>3 in one row?
Comment 5 Heiko Tietze 2020-02-04 14:59:16 UTC
(In reply to Heiko Tietze from comment #4)
> Why not just take the line breaks as normal breaks when converting the text.
> Is it so crucial to keep 1<BR>2<TAB>3 in one row?

In particular since the line break is called "Insert Manual Row Break" in the UI.
Comment 6 Gabriele Ponzo 2020-02-04 15:11:05 UTC
Please see the first attachment: if you have several rows in a pseudo-table and then change your mind about columns width, having just newline is a matter of putting the keyboard cursor in any random point within the unique paragraph, and then adjust tabulations.

If they are several paragraphs, you have to select'em all...
I don't believe that inserting such an option, even not as a default, would be annoying someone.
Comment 7 Heiko Tietze 2020-02-04 16:28:23 UTC
Gabriele agreed that we simply make both paragraph and line breaks create a new row. We came up with the idea to have the option in the other direction when a table is decomposed into simple text. But this is a different topic, say ticket.