Bug 46770 - [cs] automatic non-breaking space after single-letter words
Summary: [cs] automatic non-breaking space after single-letter words
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Localization (show other bugs)
Version:
(earliest affected)
3.4.4 release
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2012-02-29 05:19 UTC by Jiří Pudil
Modified: 2018-09-02 22:19 UTC (History)
5 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 Jiří Pudil 2012-02-29 05:19:39 UTC
To maintain a good typography, a non-breaking space should come after single-letter prepositions and conjunctions "k", "s", "v", "z", "o", "u", and "i", in Czech. It'd be great if this could be done automatically. (Perhaps in the Localized Options in AutoCorrect?)
Comment 1 bfoman (inactive) 2012-08-07 13:14:30 UTC
Is this still an issue?
Comment 2 Jiří Pudil 2012-08-07 13:44:59 UTC
Yes, this is still an issue (using v3.5.4.2)
Comment 3 tommy27 2013-04-30 08:08:35 UTC
what about LibO 4.0.2? issue is still there?

who's in charge for the Czech localizazion of LibO?
Comment 4 retired 2013-07-17 10:26:40 UTC
Jiří Pudil: Could you please test and see if this bug is still valid when using the latest LO release http://www.libreoffice.org/download/pre-releases/ ?

If so please re-set this bug to UNCONFIRMED after adding that info. Thanks :)
Comment 5 Jiří Pudil 2013-07-28 12:33:20 UTC
Sorry it took me so long. The issue is still there in 4.1.0.4.
Comment 6 Stanislav Horacek 2013-09-12 20:13:43 UTC
I confirm that this is a valid enhancement request - status set to new.
Comment 7 Simo Kaupinmäki 2014-06-14 15:23:21 UTC
As long as LO treats no-break space (U+00A0) as a fixed-width space, this enhancement would probably cause unwanted side effects in justified text. Therefore I'm marking this issue as depending on bug 41652.