https://bugs.documentfoundation.org/show_bug.cgi?id=127469
--- Comment #4 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> ---
(In reply to V Stuart Foote from comment #2)
You'll remember support for .ase is already provided (bug 84002) [1]
--except we don't do CIE-LAB colors so your .ase when placed in the
share/palette directory will give black swatches.
I did not know, also because help finds nothing for "import color".
Conversion of the RGB color values for the Corel .color palette is a simple
text edit to change to .soc
Also having to manipulate some files in the profile directory is not what I'd
call "importing a palette". Why not add some UI (and help text) for that?
The other palettes you list also look to be CIE-Lab space, or CMYK which
would not come in directly, needing internal conversion to RGB to be used.
Agreed, I don't know that details of internal color handling in LibreOffice.Is
it sRGB or completely uncalibrated?
Otherwise do not see this a appropriate. Use an external tool to build to
RGB/sRGB palette and format as .SOC (or .SOG) we can consume it then.
See above on UI and help text. In addition help knows nothing about ".ase" or
"ase". So how should the user know?
=-ref-=
[1] https://gerrit.libreoffice.org/#/c/14661/
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 127469] Allow import of color palettes in some "popular" formats · bugzilla-daemon
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.