LeaFrock
SkiaSharp `3.119.0` is released. With the wasm workload installed, the ScottPlot works well at .NET 9 Blazor WASM. ```xml ``` The `HarfBuzzSharp.NativeAssets.Linux` and `SkiaSharp.NativeAssets.Linux.NoDependencies` are optional to keep all skia-related...
@caterryan Oh, I guess you are missing the [wasm-tools](https://learn.microsoft.com/en-us/aspnet/core/blazor/webassembly-build-tools-and-aot?view=aspnetcore-9.0). Please run the command `dotnet workload install wasm-tools` in your project. Wait patiently for the command line to finish, and then...
Reinstall the wasm-tools. If you're using VS, restart it to make the tools actually work after the installation. > The version of the native libSkiaSharp library (119.0) is incompatible with...
理解您对版本兼容性的考虑。我心中的理想设计是暴露一个分词的接口，让用户通过接口实现来决定怎么分词（接口由Nuget包OpenCC.NET.ZhSegment.Abstraction提供），从而实现解耦。您可以提供基于Jieba的类作为接口的默认实现，以Nuget包（OpenCC.NET.ZhSegment.Jieba）来提供—— * OpenCC.NET.Core： 封装原版OpenCC的API * OpenCC.NET.ZhSegment.Abstraction： 提供分词接口 * OpenCC.NET.ZhSegment.Jieba：提供基于jieba的具体实现，依赖OpenCC.NET.ZhSegment.Abstraction包 * OpenCC.NET： 将分词和转换结合的包，依赖OpenCC.NET.Core和OpenCC.NET.ZhSegment.Abstraction包 这样用户既可以直接安装后2个包投入生产，也可以使用最后1个包+自定义接口实现，也可以只基于第1个包自己决定如何翻译。 当然这是我个人的浅见。那么考虑到兼容性，换个思路：现在可否另行提供不依赖分词的纯封装原版OpenCC的Nuget包（上述的OpenCC.NET.Core）呢？ > 因为转换需要依赖分词，比如”头发“和”发生“ 请问C++原版是怎么处理的您有了解吗？我不熟悉C++，我看了其他语言如js和java的实现，似乎都没有包含某个具体的分词依赖？
我看了下，原版内置了部分segment的实现。 > 这个库是我读书时候写的，很多地方都不成熟，我有时间研究研究你这个方案。 感谢开源 😄
This issue shall be pinned so that more users know the situation and discuss the future.
The .NET ecosystem is vast and vibrant, and it should not rely solely on Microsoft for everything. Open-source projects like NAudio are a testament to the community's ability to create...
I find `Font.Detect('汉')`(Chinese) will return `string.Empty` in Blazor WASM too. The default font name is `Noto Mono`. Do you know the reason? What can we do if the detect fails?
I've found a way to solve the font problem and it should be meaningful to add some intro on `IFontResolver` to cookbook. SkiaSharp loads the default font from its environment....
There're some other small issues during the solution investigation. But they're in another topic and I'll look into them when I have more free time.