Bug 36637 - Allow different FORMATTING for each string element in =CONCATENATE()
Summary: Allow different FORMATTING for each string element in =CONCATENATE()
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.3.1 release
Hardware: x86-64 (AMD64) Linux (All)
: low enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 06:22 UTC by Elias Probst
Modified: 2012-08-31 10:05 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example spreadsheet document using concate (18.36 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-04-27 08:56 UTC, Elias Probst
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Probst 2011-04-27 06:22:43 UTC
When creating a string out of several components using something like:
=CONCATENATE("A string";B10;"another string")
neither the
Comment 1 Elias Probst 2011-04-27 06:25:39 UTC
Sorry, accidentally clicked 'Submit' while still typing the description.

Here again the complete description:
When creating a string out of several components using something like:
=CONCATENATE("A string";B10;"another string")
the string cannot be formatted partially like it can be done with regular text in cells, where something like this is easily possible (using HTML markup to describe the formatting):

This is a <span style="font-style: italic;">long and partially formatted</span> string.

This doesn't work at all for concatenated strings.
Comment 2 Rainer Bielefeld Retired 2011-04-27 08:34:21 UTC
@Elias Probst:
Please attach a sample document demonstrating your needs with a "real life" example!
Comment 3 Elias Probst 2011-04-27 08:56:33 UTC
Created attachment 46125 [details]
Example spreadsheet document using concate

This is a document I quickly put together.
It basically resembles the idea of a large configuration guide document we're using in a company project, where some centrally defined information (username, hostnames, certificate IDs, ...) are used over and over again during the whole configuration process.
Formatting is used to highlight the relevant information in the instructions.
The 2nd section in the example document which actually uses =CONCATENATE() is way harder to read due to the partially missing highlights of the relevant information than the 1st section which just uses plain text withouth any cell functions.
Comment 4 Rainer Bielefeld Retired 2011-04-27 10:37:46 UTC
@Elias Probst:
May I summarize that you would like to set formatting separately for each element A,B,C in the =concentrate(A;B;C)?
Comment 5 Kohei Yoshida 2011-04-27 13:08:06 UTC
I'm afraid that's a current known limitation.  A formula result cannot be rich rext, and text that contains several formatting runs is considered rich text.
Comment 6 Elias Probst 2011-04-27 13:46:13 UTC
(In reply to comment #4)
> @Elias Probst:
> May I summarize that you would like to set formatting separately for each
> element A,B,C in the =concentrate(A;B;C)?

That's correct!
Comment 7 Elias Probst 2011-04-27 13:49:23 UTC
(In reply to comment #5)
> I'm afraid that's a current known limitation.  A formula result cannot be rich
> rext, and text that contains several formatting runs is considered rich text.

Hmm, yes... I remember another restriction which I stumbled upon some days ago, which may be related to the general handling of formula results.
Having line breaks in =CONCATENATE() is also impossible, when doing something like this:

=CONCATENATE("Some text including
line
breaks";
A5;
"And some more line-
breaks")

So it looks like this is a WONTFIX at the moment and needs some basic refactoring of the formula result stuff - maybe even clarification through OpenDocument standards, whether something like this is defined at all in the standard.
Comment 8 Rainer Bielefeld Retired 2011-04-27 21:59:00 UTC
Might be useful for particular applications, but currently I can not see important applications used by many users.

May be you should file another report for the line break observation and we will see to where that will lead?
Comment 9 Björn Michaelsen 2011-12-23 12:01:13 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 10 Florian Reisinger 2012-08-14 14:01:05 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 11 Florian Reisinger 2012-08-14 14:02:12 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 12 Florian Reisinger 2012-08-14 14:06:50 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 13 Florian Reisinger 2012-08-14 14:08:54 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian