Bug 34142 - Calc language identification should be similar to Writer's
Summary: Calc language identification should be similar to Writer's
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.0 Beta2
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: target:24.8.0
Keywords:
: 109325 (view as bug list)
Depends on:
Blocks: Statusbar Unify-Across-Apps Calc-Enhancements
  Show dependency treegraph
 
Reported: 2011-02-10 09:07 UTC by Christophe Strobbe
Modified: 2024-02-01 16:21 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Strobbe 2011-02-10 09:07:21 UTC
In LibO Writer, the user can set the language for the whole document, for a
paragraph (the current paragraph) or just a selection through the menus Tools >
Language > For Selection / For Paragraph / For all Text.
In Calc, there is no similar menu item. Apparently, language needs to be set
by setting the default language in Tools > Options > Language Settings >
Language, i.e. you set the language for your next spreadsheet. There are two
problems with this:
* the language is not visible in the status bar (unlike Writer)
* there is no mechanism to identify the language of content in languages other
than the default language (for example, in a spreadsheet with vocabulary or localisation strings where each column is in another language).
Setting the correct language for a spreadsheet and for any content in other
languages is essential for accessibility, especially for persons who rely on
text-to-speech and/or Braille (not just blind people; dyslexics also use
text-to-speech).
It would be great if this could be added to Calc.
Comment 1 ljelly 2011-06-01 03:57:09 UTC
I think this is an excellent suggestion that should be flagged to the Document Foundation for Developers to fix. 
As language support is vitally important for students that learn languages and are able to create spreadsheet tables in different languages to understand the spelling of new words.
Comment 2 Don't use this account, use tml@iki.fi 2011-06-01 05:36:35 UTC
Are you serious? "highest" importance?
Comment 3 ljelly 2011-06-02 00:45:31 UTC
I have flagged it as highest importance because I think it is just a little feature which TDF, can change in Calc, so that people learning or who have learn't languages can make effective use of other language dictionaries in the various programs of that LibreOffice has to offer when working with different languages in Calc Impress not just writer. I'm sure there is a fix that is as easy as 123. If it is already implemented in Writer I'm sure it can be developed in Calc.

The most difficult problem is finding a protocol that allows the use of switching between all of those languages without implementing more languages for the other programs. Making the one language system useable in all of the programs. So that it saves space for LibreOffice. 

(In reply to comment #2)
> Are you serious? "highest" importance?
Comment 4 Don't use this account, use tml@iki.fi 2011-06-02 01:06:20 UTC
It isn't the TDF which is doing any coding. Code contributors might be, or not, members of the TDF. Sure, the TDF can try to influence the companies and individuals that do the actual coding what new features to implement.

> I'm sure there is a fix that is as easy as 123.

Why don't you submit a patch then?
Comment 5 ljelly 2011-06-03 21:52:58 UTC
(In reply to comment #4)
> It isn't the TDF which is doing any coding. Code contributors might be, or not,
> members of the TDF. Sure, the TDF can try to influence the companies and
> individuals that do the actual coding what new features to implement.
> 
> > I'm sure there is a fix that is as easy as 123.
> 
> Why don't you submit a patch then?

I am not experienced in coding, but I do know that there are some very important features that should be fixed in LibreOffice, and I think this is one of them.
As it is remarkable how you cannot switch languages immediately in other applications in LibreOffice like you can in Writer.
I think that problem needs to be addressed importantly.
Comment 6 Rainer Bielefeld Retired 2011-06-10 02:57:13 UTC
RC2 is bit by bit identical with release version, so separate items in the version picker are useless. Changes have been discussed with Michael Meeks.
Comment 7 ljelly 2011-07-15 23:04:18 UTC
(In reply to comment #6)
> RC2 is bit by bit identical with release version, so separate items in the
> version picker are useless. Changes have been discussed with Michael Meeks.

LibreOffice Calc 3.4.2 RC 1

Ubuntu 11.10 Alpha 2

I am using this machine as a testing environment at the moment. 

But I have managed to use the dictionaries supplied in LibreOffice while using Calc.
To Change the language in a cell or column you can select the cell or the whole column and go to Format Cells and under the heading 'Font' you will be able to change your language for that selection in your spreadsheet, which will have the corresponding dictionaries. I think there needs to be a better implementation of Language Selection in LibreOffice Calc, something that is coherent and similar to the implementation in LibreOffice Writer.
Comment 8 ljelly 2011-07-15 23:06:26 UTC Comment hidden (obsolete)
Comment 9 Björn Michaelsen 2011-12-23 11:42:53 UTC Comment hidden (obsolete)
Comment 10 Scott M. Sanders 2011-12-30 06:22:49 UTC
It persists in 3.5.0beta2. It is an enhancement request, not a bug.
Comment 11 Joel Madero 2014-07-13 01:33:29 UTC Comment hidden (obsolete)
Comment 12 Christophe Strobbe 2014-07-14 09:56:06 UTC
I reconfirm the bug in LibreOffice Calc 5.2.5.2 on Windows 7 (32 bits). I.e. it is still not possible to set the language of a spreadsheet or individual cells through Tools > Language > ..., and there is still no language identification in the status bar. 

I can think of only one workaround for language identification in cells: 
* Create a new style and give it a name that is based on the language you want to use it for (e.g. lang_es for Spanish cell content);
* In the cell style dialog, go to the Font tab and set the corresponding language;
* Define a formatting (under Font, Font Effects, Background, whatever you prefer) that visually distinguishes the style from styles for other languages.
* After creating the style, you can apply the style to cells to set them to a certain language (e.g. apply the style lang_es to Spanish content, lang_de to German content, etc.). When you are done with the content, you can set the styles to a "normal" formatting (e.g. if Spanish cells had a yellow background, you can set their background to "No Fill" again).
Comment 13 Aron Budea 2017-07-24 22:38:13 UTC
*** Bug 109325 has been marked as a duplicate of this bug. ***
Comment 14 Commit Notification 2024-01-26 18:40:47 UTC
Henry Castro committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/b8bc9518d523cff59e238f1eefc4ce7e7c844196

tdf#34142: fix cell language status

It will be available in 24.8.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 15 Commit Notification 2024-01-26 18:41:49 UTC
Henry Castro committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/966f075a332b38a2689dad317d5d3c3fa61a1efb

tdf#34142: update status language after the cell format language change

It will be available in 24.8.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 16 Buovjaga 2024-02-01 16:21:42 UTC
Can this be closed as fixed now?