-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
support for .properties file syntax #970
Comments
It's similar to |
It's similar, yes, but but not identical. |
I just had an idea, based upon @mAAdhaTTah 's comment. If someone could simply copy the |
You could run: Prism.languages.properties = Prism.languages.ini right after including Prism. Once eventually there is a proper definition for this language, you remove the line. Would that work for you? |
You mean insert some sort of custom JavaScript every time I include |
Or you can just insert it at the end of prism.js, but that means it's more of a hassle to update Prism. |
Oooh! So can I fork Prism and make a pull request with |
If you can wait til the end of the week, I will merge PR #980 |
Oh, sure, that would be awesome! There's no emergency on my part---I was just wanting to register the issue so it could be addressed. Let me know when it is merged so that I can update my documents with the correct Prism language ID. Thanks!! |
@garretwilson It is merged. ;) |
It seems to work great, @Golmote ! Thank you so much for your work on this. In the next month or two I plan on trying to build my own Prism language plugin for another format, so maybe I'll send you a private note later for you to give me some pointers. All the best. |
Surprisingly I just noticed that there seems to be no support for the ubiquitous Java properties file format. Am I missing it under a different name?
The text was updated successfully, but these errors were encountered: