Skip to content

Commit 6119d36

Browse files
committed
Update the readme and fix some typos
1 parent 8f0fd06 commit 6119d36

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,15 +22,15 @@ User who use SVGKit or have to support iOS 8+(macOS 10.10+) can still use that S
2222

2323
## Note for CoreSVG framework
2424

25-
So far (Xcode 11.4 && iOS 13.4), the CoreSVG.framework is still in private framework. I've already send the feedback radar to ask for the public for this framework. If you want, please help us as well to fire radars as well: https://feedbackassistant.apple.com/
25+
So far (Xcode 11.4 && iOS 13.4), the CoreSVG.framework is still in private framework. I've already send the feedback radar to ask for the public for this framework. If you want, please help us to fire radars and request to Apple as well: https://feedbackassistant.apple.com/
2626

2727
The CoreSVG.framework API is stable and match the same concept as CoreGraphics's PDF API, so it's no reason to keep private. And we've already submitted Apps which use the CoreSVG to render the vector images on App Store.
2828

2929
All the SPI access here we use the runtime access and early check, even if future OS upgrade break the function, this framework will not crash your App and just load failed. I'll keep update to the latest changes for each firmware update.
3030

3131
If you still worry about the SPI usage, you can use [SDWebImageSVGKitPlugin](https://github.com/SDWebImage/SDWebImageSVGKitPlugin). But we may not response to any parser or rendering issue related to [SVGKit](https://github.com/SVGKit/SVGKit), because it's already no longer maintained.
3232

33-
There is also another solution: [SVG-Native](https://w3c.github.io/svgwg/specs/svg-native/index.html), a new W3C standard from Adobe, which is a subset of SVG/1.1. Both Apple/Google/Microsoft already join the agreement for this standard, you can try to write your own coder with the [code from SVG-native-viewer](https://github.com/adobe/svg-native-viewer/blob/master/svgnative/example/testCocoaCG/SVGNSView.mm) and adopt SVG-native for vector images.
33+
There is also another solution: [SVG-Native](https://w3c.github.io/svgwg/specs/svg-native/index.html), a new W3C standard from Adobe, which is a subset of SVG/1.1. Both Apple/Google/Microsoft already join the agreement for this standard, you can try to write your own coder using code from [SVG-native-viewer](https://github.com/adobe/svg-native-viewer/blob/master/svgnative/example/testCocoaCG/SVGNSView.mm) and adopt SVG-native for vector images.
3434

3535
## Example
3636

@@ -124,7 +124,7 @@ In most cases, vector SVG is preferred. But however, sometimes you may want the
124124

125125
By default it use the SVG viewBox size. You can also specify a desired size during image loading using `.imageThumbnailPixelSize` context option. And you can specify whether or not to keep aspect ratio during scale using `.imagePreserveAspectRatio` context option.
126126

127-
Note: Once you pass the pixel size, we will always generate the bitmap representation even on iOS/tvOS 11+. If you want the vector format, do not pass them, let `UIImageView` to dynamically stretch the SVG.
127+
Note: Once you pass the `imageThumbnailPixelSize`, we will always generate the bitmap representation. If you do want the vector format, do not pass them, let `UIImageView` to dynamically stretch the SVG.
128128

129129
+ Objective-C
130130

@@ -170,7 +170,7 @@ if svgImage.sd_isVector { // This API available in SDWebImage 5.6.0
170170

171171
1. The CSS `color` does not support hex syntax. Use `rgb` or `rgba` instead
172172
```html
173-
<path d="M399.8,68.2c77.3,3.1,160.6,32.1" fill=rgb(255,255,255) />
173+
<path d="M399.8,68.2c77.3,3.1,160.6,32.1" fill="rgb(255,255,255)" />
174174
```
175175

176176
## Backward Deployment

0 commit comments

Comments
 (0)