Bug 118749 - New AutoCorrect rule for copyleft symbol
Summary: New AutoCorrect rule for copyleft symbol
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
6.1.0.1 rc
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Font-Rendering AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2018-07-13 17:18 UTC by Volga
Modified: 2023-09-21 12:31 UTC (History)
6 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 Volga 2018-07-13 17:18:03 UTC
Description:
Unicode introduced copyleft symbol in June 2018, it was often used in some "copyleft" declarations, the code point is U+1F12F.
http://blog.unicode.org/2018/06/announcing-unicode-standard-version-110.html
https://www.unicode.org/charts/PDF/U1F100.pdf
https://www.unicode.org/L2/L2016/16059-copyleft.pdf

We are already having an AutoCorrect rule for copyright symbol: :copyright: → ©, thus there is a good choice to help users input copyleft symbol:

    :copyleft: → 🄯

Once we implemented, it would be nice if LibreOffice have a way to promote copyleft works.

Steps to Reproduce:
-

Actual Results:
-

Expected Results:
-


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 tommy27 2018-07-14 05:20:01 UTC
valid enhancement request.

@Laszlo Nemeth
this should be an easy hack for you.
Comment 2 V Stuart Foote 2018-07-14 16:48:50 UTC
Hmm, not so sure about getting in front of this.

We can't simply add to the Auto-correct pairs because no font present in LO will support the glyph! UI for Auto-correct gets a broken "unknown glyph" in the process.

Implementing for the Unidoce 1F12F - COPYLEFT codepoint from the Unicode 11.0 "Enclosed Alphanumeric Supplement" SMP would also require that the we provide the glyph.

IMHO this requires an early addition to our Symbol font where we should supplement PUA mapping of ®, ©, and ™

We have PUA FOD2/F0E2 Registered and PUA F0E2/F0E3 Copyright and PUA F0D4/F0E4 Trademark, and their mapping to U+00AE, U+00A9, U+2122 which probably could be cleaned up--not sure how the Serif/Sanserif selection out of the PUA gets done when selecting the glyph to use.

Then include the new Unicode 11.0 1F12F codepoint for the Copyleft in both Serif/Sanserif to match the other glyphs.
Comment 3 V Stuart Foote 2018-07-14 17:28:51 UTC
(In reply to V Stuart Foote from comment #2)

> IMHO this requires an early addition to our Symbol font where we should
> supplement PUA mapping of ®, ©, and ™
> 

s/Symbol/OpenSymbol/

> We have PUA FOD2/F0E2 Registered and PUA F0E2/F0E3 Copyright and PUA
> F0D4/F0E4 Trademark, and their mapping to U+00AE, U+00A9, U+2122 which
> probably could be cleaned up--not sure how the Serif/Sanserif selection out
> of the PUA gets done when selecting the glyph to use.

scratch all that about the F0xx mappings, I was looking "Symbol" font with its PUA mappings rather than the OpenSymbol which does map onto the U+00AE, U+00A9 and U+2122 for its corresponding PUA E024, E021, E143.
Comment 4 BogdanB 2023-09-21 05:54:50 UTC
If I write U+1F12F and press Alt+X it is getting copyleft symbol with Liberation Serif, Carlito, so on....

Was this bug solved meanwhile?

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a34dcd03254480927c403d904c0e754802d97b90
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 5 V Stuart Foote 2023-09-21 12:31:33 UTC
(In reply to BogdanB from comment #4)
> If I write U+1F12F and press Alt+X it is getting copyleft symbol with
> Liberation Serif, Carlito, so on....

That is a result of os/DE font fallback not from the font in use within the paragraph (i.e. it is NOT in Liberation Serif) and fallback falters when there are limited instances of fonts with glyph coverage.  On my Win10 laptop only an installed Libertinus family and a recent Symbola release cover. 

> 
> Was this bug solved meanwhile?
> 

No. Request was to deliver with an :Emoji: style autocorrection, that has not been done and would be a problem requiring assurance of a project delivery of a useable character for any new definition(s).  Probably by addition to OpenSymbol which we need for the Math module and general list bullets.