[Libreoffice-ux-advise] [Bug 104052] Add LibreColour HLC palette

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104052

--- Comment #56 from Christoph Schäfer  ---
(In reply to Stephan Bergmann from comment #45)
> (See the discussion at
>  html> "Allow extensions to provide color palettes" for a potential way of
> providing this palette as a .oxt extension.)

Hi Samuel,

Thanks for your support!

We might find another solution, but since you were at it, do you think you
could create an Extension that includes the next version of the Open Colour
Systems Collection 2.0, a huge collection of mostly commercial colour systems,
i.e. 376 SOC palettes?

OCSC 2.0 will probably be released during the next few days, and freieFarbe /
freeColour would be glad if someone could volunteer to create an Extension with
all those CC-licensed palettes.

OCSC also has its own logo (SVG).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104052] Add LibreColour HLC palette

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104052

--- Comment #55 from Christoph Schäfer  ---
(In reply to Taylor Jenkins from comment #54)
> Created attachment 129558 [details]
> Comparison between hlcfaecher.pdf & LO Writer w/ librecolour.soc
> 
> This is a screenshot with the hlcfaecher.pdf color swatch on the left, the
> corresponding color in LO from librecolour.soc in the the middle, and the
> color in LO using the hex value shown in the pdf, on the right. When the two
> different hex values are shown side by side in LO, they are not noticeably
> different on my monitor. Curious why the pdf was noticeably different, I
> used a color picker to determine the actual color value, which is shown
> overlaid on the pdf color swatch.

Colour pickers aren't reliable. 

We are aware of minor differences between the sRGB/Hex values in the fans and
the SOC files. That's a problem of the algorithms and colour management systems
used for the conversion from CIELAB to sRGB. The colour fans have been produced
with Photoshop on Windows, hence the values according to Adobe's native CMS.
The converter we used to create the SOC files, however, was using littleCMS2,
which is much more precise than Adobe's outdated CMS.

In practice it doesn't matter much, though, because in RGB values, the
deviation isn't huge, one or two digits in one or two channels at most, which
is within the acceptable error margin, given the diversity of devices or output
targets.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104206] Allow Paragraph Styles to bind to List Styles' levels, like with Outline Numbering

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104206

--- Comment #3 from Mike Kaganski  ---
(In reply to Regina Henschel from comment #2)

Thank you for considerations!

> Please examine ODF and its concepts of outline and lists and discuss file
> format solutions very early.

You are absolutely right.
However, I hope, and my vision is, that my proposal can be implemented without
modifying the ODF standard at all.

I must say that I see this as UI-only concept. From the user PoV, the binding
between a paragraph style and a list style is what program does when user sets
the style or changes list level. I suppose that the bond may be defined in ODF
by using application-specific extended tags in corresponding styles, and then
modifying the app behavior in relevant places. The ODF output should stay
unmodified (modulo the extended style properties to keep the bond between
sessions).

So, the output file should have normal list and outline structure, so it will
be open with any previous version, or with other ODF viewer, without problems;
the only missing thing in those older/alien versions will be the bond loss and,
thus, need to make all style-to-level adjustments manually.

> >I suppose that it could be made a GSoC project task.
> Do you will mentor it?

It would be an honor for me. I may only hope that I can succeed in this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104206] Allow Paragraph Styles to bind to List Styles' levels, like with Outline Numbering

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104206

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de

--- Comment #2 from Regina Henschel  ---
Please examine ODF and its concepts of outline and lists and discuss file
format solutions very early.

(In reply to Mike Kaganski from comment #0)

> When a paragraph style is associated with Outline Numbering level, its
> "Outline & Numbering" property page controls for Numbering style and Outline
> level become disabled.
More exact, if it gets the default outline numbering via Tools > Outline
Numbering.

> 
> OTOH, any paragraph, that is not used in Outline Numbering, may be
> associated with a list style using controls on that property page. This
> allows paragraphs with that paragraph style to become numbered using
> selected list style, and retain the paragraph style on changing list's level.
"associated with a list style" is not exact enough. You need to distinguish,
whether the paragraph has got an outline level or not on that property page.


> 
> The proposal is the following: to allow paragraph style to optionally
> specify selected list style's level at the Outline & Numbering property
> page.

I'm not sure about this. In case of the default outline, the  has the
text:outline-level attribute. In case of a user outline it has already the same
text:outline-level attribute.

Currently in case of user outline, not the numbering-style is used, which has
the same text:level value. In case of the default outline this binding between
text:outline-level and text:level is done.


I see an additional problem: Currently a  is written, whether an
outline level is set or not. So there exists a "level" given by the 
nesting and a setting of the numbering style by the . On the other
hand, the paragraph style has a list-style-name attribute and a
default-outline-level attribute.


>I suppose that it could be made a GSoC project task.
Do you will mentor it?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104052] Add LibreColour HLC palette

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104052

--- Comment #54 from Taylor Jenkins  ---
Created attachment 129558
  --> https://bugs.documentfoundation.org/attachment.cgi?id=129558&action=edit
Comparison between hlcfaecher.pdf & LO Writer w/ librecolour.soc

This is a screenshot with the hlcfaecher.pdf color swatch on the left, the
corresponding color in LO from librecolour.soc in the the middle, and the color
in LO using the hex value shown in the pdf, on the right. When the two
different hex values are shown side by side in LO, they are not noticeably
different on my monitor. Curious why the pdf was noticeably different, I used a
color picker to determine the actual color value, which is shown overlaid on
the pdf color swatch.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 100100] Emoji toolbar control

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=100100

Akshay Deep  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=10
   ||4622

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104052] Add LibreColour HLC palette

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104052

--- Comment #53 from Taylor Jenkins  ---
(In reply to V Stuart Foote from comment #52)
> 
> Unfortunately, I've noticed there are considerable differences between the
> sRGB Hex values used in your .soc palette, and the sRGB Hex values indicated
> on the PDF of the freieFARBE HLCColors fan [1].
> 
> =-ref-=
> [1] http://dtpstudio.de/cielab/downloads/hlcfaecher.pdf

I agree, it appears that none of the hex values in the pdf match the hex values
in the .soc. For example, here is a line from the .soc:



The corresponding color on the pdf shows the following information:

HLC 090 90 60
Lab 90 0 60
sRGB 253 225 107 * HEX #FDE16B
CMYK 0 5 65 0

Notice how for the color name "HLC 090 90 60", the hex values do not match.
Though they are very similar, when the colors are placed side by side, they are
perceptibly different.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 52316] WRITER Page count in Status bar does not respect setting " Print automatically inserted blank pages"; Incorrect value for page count field

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=52316

--- Comment #14 from Julien  ---
Hi,
Bug still present in LibreOffice 5.2.3.2 (on ubuntu yakkety, Build ID:
1:5.2.3~rc2-0ubuntu1~yakkety1)
Regards, Julien

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 90792] Enable toolbar code to load HiDPI bitmaps

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=90792

Yousuf Philips (jay)  changed:

   What|Removed |Added

 Blocks||103239


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103239
[Bug 103239] [META] Toolbars bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104300] Main menu does not have button "»"

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104300

Yousuf Philips (jay)  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |philip...@hotmail.com
   |.freedesktop.org|
 Blocks||85811


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=85811
[Bug 85811] [META] Main menu bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104510] Go to page dialog (Ctrl-g) should appear in the top right corner

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104510

Yousuf Philips (jay)  changed:

   What|Removed |Added

   Keywords|needsUXEval |
 Status|UNCONFIRMED |RESOLVED
 CC|libreoffice-ux-advise@lists |
   |.freedesktop.org|
 Blocks||102019, 83054
 Resolution|--- |WONTFIX

--- Comment #3 from Yousuf Philips (jay)  ---
As when the go to page dialog is open the document isnt accessible, opening the
go to page dialog in the center is the correct behaviour.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83054
[Bug 83054] Add "Go to Page" Entry in Edit Menu
https://bugs.documentfoundation.org/show_bug.cgi?id=102019
[Bug 102019] [META] Dialog bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 36019] Security: Add some way to dynamically enable/ disable extension installation.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=36019

Yousuf Philips (jay)  changed:

   What|Removed |Added

   Keywords|needsUXEval |
 CC|libreoffice-ux-advise@lists |drich...@largo.com
   |.freedesktop.org|

--- Comment #11 from Yousuf Philips (jay)  ---
(In reply to Muhammet Kara from comment #10)
> I agree with you on keeping the scope only to the GUI. If we disable the
> buttons, we can add a notice somewhere on the extension manager. Or we leave
> the buttons clickable, and show a message whenever the user clicks on them.

Disable the buttons and add a text label notice above the buttons in red (which
of course is hidden when extension installation is enabled) stating that the
feature has been disabled in expert configuration.

@Dave: Any thoughts?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 79787] Normal cell borders are showing dashed/ dotted when export to xlsx/xls and reopen in MSO

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=79787

Yousuf Philips (jay)  changed:

   What|Removed |Added

 Status|RESOLVED|NEW
 Resolution|WONTFIX |---

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104052] Add LibreColour HLC palette

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104052

V Stuart Foote  changed:

   What|Removed |Added

 CC||christoph-schae...@gmx.de

--- Comment #52 from V Stuart Foote  ---
The extension is cool, thanks Samuel!  But before we put this to bed have a
technical question for Christoph.

Unfortunately, I've noticed there are considerable differences between the sRGB
Hex values used in your .soc palette, and the sRGB Hex values indicated on the
PDF of the freieFARBE HLCColors fan [1].

Each HLC color I checked, entering the CMYK value in LibreOffice's color picker
for the HLC swatch returns the sRGB as indicated for the color on the PDF.
Entering your sRGB returns different CMYK.

Which are the correct sRGB that should go into a OpenOffice SOC palette? If it
is the sRGB from the HLC colorfan, the new extension based on your SOC is not
going to match the fans for process color use the way you'd hoped.

=-ref-=
[1] http://dtpstudio.de/cielab/downloads/hlcfaecher.pdf

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 104052] Add LibreColour HLC palette

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=104052

Samuel Mehrbrodt (CIB)  changed:

   What|Removed |Added

 CC||s.mehrbr...@gmail.com

--- Comment #51 from Samuel Mehrbrodt (CIB)  ---
I created an extension bundling the librecolour palette and submitted it to the
extensions directory, currently awaiting review.
Extension source is here: https://github.com/smehrbrodt/librecolour-extension

Can we then mark this as closed?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise

[Libreoffice-ux-advise] [Bug 101820] DIALOG: Revise Page Style's Page tab

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=101820
Bug 101820 depends on bug 67973, which changed state.

Bug 67973 Summary: UI: change option name from "Format" to "Page Number Format" 
in dialog Page styles
https://bugs.documentfoundation.org/show_bug.cgi?id=67973

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise