Present: Thomas, Csongor, Jay, Heiko
* Vertical alignment of images anchored as character
+ https://bugs.documentfoundation.org/show_bug.cgi?id=87742
+ screenshot - https://bug-attachments.documentfoundation.org/attachment.cgi?id=111368
+ WF because alignment depend on use case; center is as good as top (Heiko, Csongor)
+ Top is better than centered, ideally first line at top, last at bottom (Thomas)
=> no objection but not worth the effort
* Toggle read access at statusbar
+ https://bugs.documentfoundation.org/show_bug.cgi?id=86303
+ no need for this feature in the sb => WF (Heiko)
+ use case: multiple open documents where some are secured by the function (Csongor)
+ 2x pro the suggestion, 1x no opinion, 1x con
=> go
* Shortcut for Double Underline in all modules
+ https://bugs.documentfoundation.org/show_bug.cgi?id=113939
+ if we do that it requires to switch from ctrl+D to shift+ctrl+U in Writer (Heiko)
+ advantage of consistency but have a better shortcut (Thomas)
=> go with shift+ctrl+U for double underline for all modules
* Change string from 'Left' to 'Default' or 'Start' or code 'Right' entry
+ https://bugs.documentfoundation.org/show_bug.cgi?id=98211
=> postponed for Stuart
* Removal of tango, breeze and libreoffice palettes
+ https://bugs.documentfoundation.org/show_bug.cgi?id=113858
+ at least LibreOffice should remain as it is our branding (Heiko)
+ Thomas, Jay pro cleaning up
+ keep LibO, remove Tango/Breeze (Csongor)
+ better names for LibO? (Thomas)
+ idea has been refused last year https://bugs.documentfoundation.org/show_bug.cgi?id=104053
=> keep going
* Removal of Open Sans, PT_Serif, Source Sans/Code fonts (Jay)
+ https://bugs.documentfoundation.org/show_bug.cgi?id=103080
+ ESC were against removing of Libertine and DejaVu
+ would still like to remove Open Sans, PT_Serif, Source Sans Pro
and Source Code that were added in 4.0 and 4.4 now that we are
bundling Noto Sans and Noto Serif families.
+ we dont bundle Source Serif Pro as it isnt available in italics
https://bugs.documentfoundation.org/show_bug.cgi?id=79022
+ like many different fonts (Csongor)
+ hate many different fonts, esp. when not installed via distro management (Heiko)
+ no opinion, don't like too much very similar fonts (Thomas)
+ be mindful of fallback for unique glyphs, U+1f512 for example--Source Code Pro our only
location (Stuart)
+ what did we do before Source Code Pro was added in 4.0? (Jay)
+ shove them into OpenSymbol, the Emoji support has been painful (Stuart)
=> AI: ESC should confirm removal of the three
* Optimal column width
+ https://bugs.documentfoundation.org/show_bug.cgi?id=113604
(auto size behavior, "style" instead of direct formatting)
+ https://bugs.documentfoundation.org/show_bug.cgi?id=113960
(table properties: col sizing tedious)
+ solution could include UI proposal from
https://bugs.documentfoundation.org/show_bug.cgi?id=113603
+ Working With Tables in Writer -
https://docs.google.com/document/d/1D212Ihf8BYVOa1VjSPifq4sO_Cq4CZPhC0vya68zk3c
=> would be a cool GSoC project, needs a design session
=> keep tickets but do not make small patches
--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-design] Minutes from the design/UX meeting 2017-Nov-22 · Heiko Tietze
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.