Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SharpFont/FreeType backend does not like non-ascii filenames #49

Open
HinTak opened this issue Jul 14, 2017 · 2 comments
Open

SharpFont/FreeType backend does not like non-ascii filenames #49

HinTak opened this issue Jul 14, 2017 · 2 comments

Comments

@HinTak
Copy link

HinTak commented Jul 14, 2017

This was filed upstream around when FontVal 2.0 was in testing about a year ago:
Robmaister/SharpFont#89

This was fixed two months ago:
Robmaister/SharpFont#112

and backported:
Robmaister/SharpFont#89 (comment)

This is mostly a note to for people who are still using 2.0 to upgrade as soon as 2.1 is out.
@HinTak
Copy link
Author

HinTak commented Jul 16, 2017

Two-part fixes in the upcoming v2.1 .

@HinTak HinTak closed this as completed Jul 16, 2017
HinTak added a commit to HinTak/Font-Validator that referenced this issue Jul 20, 2017
@HinTak
SharpFont, 4.0.1+fixes, v3.0.1-81-gc574260, TargetFrameworkVersion=v2…
7d037db 
….0 build

net4 build of SharpFont, 4.0.1+fixes from HinTak/SharpFont:v3.0.1-75-ge1b444c

    cd Source/SharpFont && xbuild SharpFont.csproj

[email protected]:HinTak/SharpFont.git v4.0.1+fixes v3.0.1-80-g670aa0b

    cd Source/SharpFont && xbuild /p:TargetFrameworkVersion=v2.0 /property:Configuration=Release SharpFont.csproj

4.1.0+fixes need to do without dll

upstream addition 8efddb79a3d55bca01e5e80e8f3782e8f8c5fbab

xbuild /p:TargetFrameworkVersion=v2.0 /property:Configuration=Release SharpFont.csproj ; v3.0.1-81-gc574260

Part of the fixes to
microsoft#49
Robmaister/SharpFont#89
and is built for dotnet2:
microsoft#42
See also:
Robmaister/SharpFont#95
and also
Robmaister/SharpFont#82
HinTak added a commit to HinTak/Font-Validator that referenced this issue Jul 20, 2017
@HinTak
fix problems with marshalling
a6f2c97 
Conflicts:
	Compat/Compat.cs

marshalling part 2

2nd part of the fixes to
microsoft#49
@HinTak HinTak reopened this Sep 6, 2018
@HinTak
Copy link
Author

HinTak commented Sep 6, 2018

change unhooked with 2.1 due to instability.

@HinTak HinTak mentioned this issue Sep 6, 2018
Closed
HinTak added a commit to HinTak/Font-Validator that referenced this issue Jul 19, 2022
@HinTak
SharpFont, 4.0.1+fixes, v3.0.1-81-gc574260, TargetFrameworkVersion=v2…
f22045b 
….0 build

net4 build of SharpFont, 4.0.1+fixes from HinTak/SharpFont:v3.0.1-75-ge1b444c

    cd Source/SharpFont && xbuild SharpFont.csproj

[email protected]:HinTak/SharpFont.git v4.0.1+fixes v3.0.1-80-g670aa0b

    cd Source/SharpFont && xbuild /p:TargetFrameworkVersion=v2.0 /property:Configuration=Release SharpFont.csproj

4.1.0+fixes need to do without dll

upstream addition 8efddb79a3d55bca01e5e80e8f3782e8f8c5fbab

xbuild /p:TargetFrameworkVersion=v2.0 /property:Configuration=Release SharpFont.csproj ; v3.0.1-81-gc574260

Part of the fixes to
microsoft#49
Robmaister/SharpFont#89
and is built for dotnet2:
microsoft#42
See also:
Robmaister/SharpFont#95
and also
Robmaister/SharpFont#82
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HinTak