alerque / libertinus

The Libertinus font family
SIL Open Font License 1.1
1.04k stars 59 forks source link

SF.net upstream bugs and feature requests #41

Open Crissov opened 8 years ago

Crissov commented 8 years ago

I see that the file /BUGS lists some of the existing issues for Linux Libertine at SourceForge as either Fixed, Invalid or Ignored, but not all of them. Should we raise the Open ones again on GitHub (if they apply) to keep better track of them?

PS: Converted table to checklist on 15 March 2021 and incorporated updates from comments below up until then.

khaledhosny commented 8 years ago

Opening issues here for the reproducible ones is fine.

khaledhosny commented 8 years ago

Needless to say that I can’t test every single one of these (especially ones that require non-Linux systems), so I need help finding reproducible one then deciding if it is a thing we need to fix or not.

Crissov commented 8 years ago

Okay, I’ll check whether the bugs I filed against Biolinum (mostly serif glyphs) still apply to Libertinus Sans. Will defer the feature requests for now.

KrasnayaPloshchad commented 7 years ago

Filling #96 #97 #98 #99

khaledhosny commented 6 years ago

Better track individual bugs. If people care enough and want to see them fixed here, they will open issues here.

alerque commented 4 years ago

@Crissov Don't be shy about opening issues for feature requests too. No promises that they will be fulfilled, but I'd rather have the issue to track what people are actually interested in than not.

Also do either you or maybe @waldyrious have a good feel for how many of these old Libertine project issues actually made their way into this bug tracker? Could this list use a once-over to find things that slipped by or has that been done and we can call it a done deal?

waldyrious commented 4 years ago

Also do either you or maybe @waldyrious have a good feel for how many of these old Libertine project issues actually made their way into this bug tracker? Could this list use a once-over to find things that slipped by or has that been done and we can call it a done deal?

I would love to help out with that sweep, but I'm afraid I won't have the bandwith to do that anytime soon. That said, I'd also ping @KrasnayaPloshchad who IIRC brought multiple requests from SourceForge to this issue tracker.

alerque commented 4 years ago

I'm re-opening this issue not to track the state of the actually bugs but just to track issue migration. I'll keep it open until we can confidently say that everything in the Linux Libertine project tracker has been reviewed and either noted that it is fixed or opened a corresponding issue here.

Since the handy table above leaves off with №324 in the SF tracker, I just worked through the ones posted since (№325–339) and noted the ones that have been fixed and open corresponding issues for the ones that were not.

alerque commented 4 years ago

Thanks @waldyrious, and there is no rush on this. I see you already triaged a few. Whenever we get around to this is fine, obviously if people were paying attention and cared they could have opened issues here themselves. That being said eventually I'd like to be able to say that we've addressed 100% of confirmed issues from the SF issue tracker.

KrasnayaPloshchad commented 4 years ago

And I fill #131 #157 here

Crissov commented 4 years ago

Unfortunately, I don't have the time to contribute to this effort at the moment.

alerque commented 3 years ago

Linux Libertine bug 229 is tracked locally now as #411.

Crissov commented 3 years ago

MUFI support, Linux Libertine bug 292, became #101 and was dismissed as out of scope.

Russian Ruble, Linux Libertine bug 309, is now part of #457 and #255.

IPA support, Linux Libertine bug 300, is tracked primarily in #438 and also in #429 (stacking diacritics).

nsemrau commented 3 years ago

frowning_face and relaxed (smileys) are too similar, Linux Libertine bug 039 got fixed by the redesign in https://github.com/alerque/libertinus/pull/307.

waldyrious commented 3 years ago

@nsemrau thanks for the heads-up! I've updated the table in the opening comment above.

nsemrau commented 3 years ago

#122 "Three exclamation marks" - Fixed on my standard LuaLaTeX '20 and LibreOffice 7.1 setups (-> Fixed)

#136 "Fonts package naming" - "Libertine" could be considered as offense in France. Rename to "Libertinus" fixed that; I'll probably eat my words soonish, but "Freed slave" in Latin shouldn't be too offensive (-> Fixed)

#157 "Standardize font naming" - With the renaming/reorganisation from Libertine to Libertinus, the font file naming is now consistent (-> Fixed)

#167 "website: unintended redirect" - Upstream only (-> Invalid)

#176 "Kerning of !!!" and #254 "Poor kerning for multiple exclamation marks" Duplicate of #122 (-> Fixed)

#211 "No build script in the source" - Libertinus has a maintained Fontship makefile (-> Fixed)

#223 "oldstyle number bold and italic 6 is like 0" - Just tested the minimal recipe and it shows the correct glyph, i.e. "6" (-> Fixed)

#229 "Linux Libertine Mono: not showing up in monospaced font list" - Gives "1" for me (LibertinusMono-Regular.otf: Libertinus Mono:style=Regular) (-> Fixed)

#237 "Libertine 5.3.0 - square bracket mismatch" - Tested in LuaLaTeX '20 - seems correctly aligned (-> Fixed)

#239 "Several ligatures produce output that is not copyable" - Successfully tested in up-to-date Okular (KDE) (-> Fixed)

#250 "ch and ck ligatures are not activated by +liga as advertised" - Still valid for c_h and c_k ligature (xelatex '20) (-> Valid)

#272 "Diacritics in Linux Libertine SemiBold" - At least still valid for the example character "p" (-> Valid)

#305 "Missing "E" in Linux Libertine Initials 5.0.6" - Works on xelatex and lualatex '20 and LibreOffice 7.1 (-> Fixed)

#309 "Require for Russian Ruble sign" Still missing (-> Valid, already tracked in https://github.com/alerque/libertinus/issues/457)

#316 "Broken links on "Files & License" page" - Outdated upstream problem (-> Invalid)

I went through the list and was able to identify a few changes.

May I please have the right to edit posts inside this repo, @alerque ? While this list might never be 100% complete, I'd like to keep an eye on it and edit in changes later accordingly (without having to hit up someone to change the status of a bug at my behest every time).

Crissov commented 3 years ago

I've edited the initial comment to reflect recent feedback.