You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we can initialize a TFHpple with an encoding parameter, one has to search through the libxml2 code to find what literal values are allowed for the encoding. This is not in keeping with the way string encoding is handled throughout Objective-C. Instead hppleWithHTMLData: encoding: and similar methods should take an NSStringEncoding enum, such as NSUTF8StringEncoding or NSISOLatin1StringEncoding, and then pass the appropriate encoding string to libxml2.
Unfortunately this would break compatibility of the API for anyone already using the new with-encoding methods; perhaps still more methods like hppleWithHTMLData: enumEncoding: should be created?
The text was updated successfully, but these errors were encountered:
Now that we can initialize a TFHpple with an encoding parameter, one has to search through the libxml2 code to find what literal values are allowed for the encoding. This is not in keeping with the way string encoding is handled throughout Objective-C. Instead hppleWithHTMLData: encoding: and similar methods should take an NSStringEncoding enum, such as NSUTF8StringEncoding or NSISOLatin1StringEncoding, and then pass the appropriate encoding string to libxml2.
Unfortunately this would break compatibility of the API for anyone already using the new with-encoding methods; perhaps still more methods like hppleWithHTMLData: enumEncoding: should be created?
The text was updated successfully, but these errors were encountered: