As follow-up to bug 96988: Users seems to be confused by this option. The recommended workflow is using Tools > Language (and/or templates, styles etc.) while the option defines the default.
(In reply to Heiko Tietze from comment #0)
Is there a way to set the document language? Currently Tools->Language->For All Text->More goes to the said Tools > Options > Language, with the "For the current document only" checkbox checked. What is the substitution, before that thing is removed?
Didn't test T>L but this should just set the language for the document as T>O>L does. So it's not just removing the checkbox, unfortunately.
Actually all three - "For Selection"/"For Paragraph"/"For All Text" - lead to confusing dialogs. Former two bring the Character dialog on Font tab, where language is just one setting among multiple. The latter one brings the said Language dialog... where the language is also not the only thing; and all that is rather counter-intuitive, and inconsistent.
I would propose to implement this in stages:
1. Create a dedicated "Set Language" dialog, with the only purpose to select the text language. It would be very simple: have only one list box with languages, OK and Cancel. It would be consistently used for all three actions.
2. When it's implemented, the checkbox (and related document-specific functionality) may be removed from Options.
This would duplicate functionality a bit: Character dialog has the control to set the language, doing the same as this proposed dialog; yet, having a streamlined UI for the *dedicated* UNO command seems logical, and convenient to end user. If needed, the dialog and/or its help could include the mention that this is the same thing that is available on Character dialog (for selection and Paragraph cases).
What do you think?
(In reply to Mike Kaganski from comment #3)
> What do you think?
+1 (statusbar offers to set installed languages per single click, menu probably too; this needs to be considered; and the new dialog's selection is taken from the current selection).
No further input, let's do it.
*** This bug has been marked as a duplicate of bug 103036 ***