We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
I tried parsing some Android XML configuration files; these have attributes, for instance, like
android:keyWidth="15%p" android:horizontalGap="0px" android:verticalGap="0px"
clj-tagsoup lowercases the attribute names-----e.g.:
android:keywidth
so that it doesn't roundtrip through Hiccup.
Additionally, it doesn't pick up the xmlns declaration in the root element; e.g:
xmlns:android="http://schemas.android.com/apk/res/android"
This has to be put back in by hand.
(I'm using Android as an example, but presumably these issues have relevance beyond Android.)
Thanks,
Nick.
The text was updated successfully, but these errors were encountered:
+1
Same issue with svg parsing: viewBox is changed to viewbox, which is not valid for svg, giving an error. Could lowercasing be optional?
viewBox
viewbox
Sorry, something went wrong.
You could fix the lowercase :viewbox like this:
(-> (pl.danieljanus.tagsoup/parse-string svg-string) (update 1 clojure.set/rename-keys {:viewbox :viewBox}))
I wonder @nathell, is the lowercasing done in clj-tagsoup or in some underlying library?
No branches or pull requests
I tried parsing some Android XML configuration files; these have attributes, for instance, like
android:keyWidth="15%p"
android:horizontalGap="0px"
android:verticalGap="0px"
clj-tagsoup lowercases the attribute names-----e.g.:
android:keywidth
so that it doesn't roundtrip through Hiccup.
Additionally, it doesn't pick up the xmlns declaration in the root element; e.g:
xmlns:android="http://schemas.android.com/apk/res/android"
This has to be put back in by hand.
(I'm using Android as an example, but presumably these issues have relevance beyond Android.)
Thanks,
Nick.
The text was updated successfully, but these errors were encountered: