Closed topazus closed 1 year ago
Hello @topazus.
I discovered that directory too. If I remember correctly, it was not containing all the information we needed to populate the internal UCD data structures.
I am not sure how you deal in the .spec file with it (in packaging). What I did for .deb file creations in sandboxed packaging is, to pre-fetch the .zip files from upstream (unicode.org) and have these packaged with the source code.
Let me see what the state is as of right now and report back ASAP.
Wow. it works. Adjusting commit incoming....
Okay. I have merged it to master. Do you need a new release for this, or is it sufficient to simply apply the commit (eb40101359cb283be0b736f6bda383243522fa91) (as patch) in the spec file?
Okay. I have merged it to master. Do you need a new release for this, or is it sufficient to simply apply the commit (eb40101) (as patch) in the spec file?
Maybe I can use a patch file at this time
Closing this since the the review request of libunicode package is approved. Thanks a lot.
yay. Many thanks for your work!
The
unicode-ucd
package in Fedora provides the same thing with the ucd download from https://www.unicode.org/Public/15.0.0/ucd/UCD.zip. The reviewer asked me to give some explanations about the UCD in the review request of libunicode on Fedora bugzilla.https://github.com/contour-terminal/libunicode/blob/f921d1baabe0714aed700657c1e6e229c9fa0db4/CMakeLists.txt#L58
I do not find a good method to deal with this. changing
${LIBUNICODE_UCD_BASE_DIR}/ucd-${LIBUNICODE_UCD_VERSION}
to/usr/share/unicode/ucd
where the UCD files provided byunicode-ucd
package can work. Any better suggestions? @christianparpartrelated issue: https://github.com/contour-terminal/libunicode/issues/56