When you set columns in a TOC or index, the spacing field should be set to a good default value rather than 0.00" so that a user doesnt need to modify this value, unless they want to be specific.
Sure -> NEW. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI
We're replacing our use of the 'ux-advise' component with a keyword: Component -> LibreOffice Add Keyword: needsUXEval [NinjaEdit]
We use the same defaults for paragraph/page columns. So any objections to go with 0.2cm for column spacing in general?
Created attachment 135839 [details] page 68 (In reply to Heiko Tietze from comment #3) > We use the same defaults for paragraph/page columns. So any objections to go > with 0.2cm for column spacing in general? The value 0.2cm is too small. The attachment is a scan from the textbock Gublins, Jürgen: Mut zur Typographie:ein Kurs für Desktop-Publishing. Springer-Verlag Heidelberg 2000, 2.Aufl. There exist no fix, correct value, but it depends on e.g. font size. The width of "mi" can be taken as a rough guide. Find a table on page 70. You will notice, that 3.2mm is the smallest value there.
Created attachment 135840 [details] page 69
Created attachment 135841 [details] page 70
Found another site supporting 0.4cm (here 1 pica): http://printwiki.org/Gutter
We discussed the topic in the design meeting today. The recommendation is to go with 0.6cm (like Calligra) as the default. Removing needsUX, and it is likely an easyhack.
Hello! I am a newbie in bug fixing,can you please help in fixing this bug?
(In reply to saran.chava143 from comment #9) > Hello! I am a newbie in bug fixing,can you please help in fixing this bug? Can you please assign me this bug to work on?
(In reply to saran.chava143 from comment #10) > Can you please assign me this bug to work on? You can "take" it yourself. Bad news is that the issue has been solved with bug 67670. The column settings of a page are the same as for TOC. The patch https://gerrit.libreoffice.org/#/c/43964/ is merged into master and will be available in 6.0. Sorry, but I'm sure you find another issue that can be fixed easily.