Contribute this lexer to Pygments

[jodischneider]

Contribute this lexer to Pygments. According to http://pygments.org/contribute/ it looks like a pull request on bitbucket will do. Appropriate place appears to be here:
https://bitbucket.org/birkenfeld/pygments-main/src/7304e4759ae65343d89a51359ca538912519cc31/pygments/lexers?at=default

[uholzer]

I will do so when I have time to do it. In order to make a pull-request, an example N3 file that makes use of all N3 features should be added. Unfortunately, I have a lot of work at the moment. (Of course you are free to contribute such an N3 file.)

[gniezen]

We could also consider submitting a pull request to Linguist (https://github.com/github/linguist), so that N3/Turtle is recognized on GitHub.

[danmichaelo]

For reference, there is an issue on this at pygments-main too: https://bitbucket.org/birkenfeld/pygments-main/issue/215/new-lexer-for-n3-turtle

(btw. I just created a pull request on Linguist using a TextMate-compatible grammar: github-linguist/linguist#1841)

[gniezen]

It looks like @danmichaelo 's work is now live on GitHub! Now any Turtle/SPARQL code posted has nice syntax highlighting! It's a pity the TextMate grammar can't be somehow converted to Pygments.

[westurner]

Thanks @danmichaelo !

[hoijui]

Pygments moved from BitBucket to GitHub, so the auto-converted issue is now there too.

[westurner]

What about also RDFstar and SPARQLstar syntax highlighting?

…

On Fri, Feb 16, 2024, 5:27 AM hoijui ***@***.***> wrote: Pygments moved from BitBucket to GitHub, so the auto-converted issue <pygments/pygments#35> is now there too. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMNS2RMS2E3I3EVRPKSSLYT4YBLAVCNFSM4AHT3LO2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJUHAYTEMJUGA4Q> . You are receiving this because you commented.Message ID: ***@***.***>

[hoijui]

@westurner I would recommend to make two new issues for that.