-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Do you know about the sass package? #1
Comments
As the Readme says, this was a PoC for dr wilke. I kinda thought the sass
pkg cld do it as well but didn’t poke at it.
…On Sat, Aug 10, 2019 at 12:44 Gábor Csárdi ***@***.***> wrote:
AFAICT it can parse CSS files. katana seems to be somewhat unmaintained
TBH.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AAD4PNXA53RZO636WNLJ4YDQD3WAFA5CNFSM4IKZ4JN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HERKCAA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD4PNQI57P5ROZA4QRY3VLQD3WAFANCNFSM4IKZ4JNQ>
.
|
I'll take a look at what the sass pkg can do. Alternatively, I think the right way forward with katana would be to not treat it as an external dependency but to just take all the code, integrate into a package, and start maintaining. Certainly beats writing a flex based parser from scratch. |
I may have been overly optimistic about katana. It doesn't include the bison/flex source files, so it's essentially unmaintainable. The maintainers have ignored requests to provide these files for about two years. I looked at sass also. I don't see how it can be used to parse CSS. At least, this functionality does not seem to be exported via R. If I'm missing something I'd be happy to be proven wrong. |
The C lib they use can most probably parse CSS, so maybe open an issue to see if they want a PR? |
Btw. there is also http://www.netsurf-browser.org/projects/libcss/ but that does not seems to be an easy thing to wrap, either. |
AFAICT it can parse CSS files. katana seems to be somewhat unmaintained TBH.
The text was updated successfully, but these errors were encountered: