[trinity-devel] kate Settings -> Syntax Highlight -> Download -> no more from kate.org - What's TDE doing?
Slavek, all
Kate-editor.org finally pulled the plug on allowing updates to the kate syntax files. Not just for KDE3, but for Frameworks5 as well. While the change was over a year ago, I don't think the link went down until sometime later.
So basically we are left with a config dialog with a [Download] button that no longer does anything anymore. It seems there needs to be a similar repository setup and a change made to the URL kate uses. While with Frameworks 5, each new version will come with the new syntax files, for TDE/KDE3 there will need to be some repository that makes updates available when things change (like the current html/css file needs help)
The files are relatively small (40k, etc..), and the number that change on an annual basis is small, so there shouldn't be much bandwidth required to support it at all -- the reality of it is very few ever update the syntax files until -- well something doesn't work any more.
I'm open to suggestions. I know we looked a difference in the javascript file ~ 2 years ago between the TDE version and openSUSE KDE3 version, and since that time kate-editor.org pulled the plug.
I would probably lean toward hooking the [Download] URL button to a git repository that could provide a more or less seamless URL change for where kate looks for the updates? Thoughts?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2020/05/13 03:25 PM, David C. Rankin wrote:
Slavek, all
Kate-editor.org finally pulled the plug on allowing updates to the kate syntax files. Not just for KDE3, but for Frameworks5 as well. While the change was over a year ago, I don't think the link went down until sometime later.
So basically we are left with a config dialog with a [Download] button that no longer does anything anymore. It seems there needs to be a similar repository setup and a change made to the URL kate uses. While with Frameworks 5, each new version will come with the new syntax files, for TDE/KDE3 there will need to be some repository that makes updates available when things change (like the current html/css file needs help)
The files are relatively small (40k, etc..), and the number that change on an annual basis is small, so there shouldn't be much bandwidth required to support it at all -- the reality of it is very few ever update the syntax files until -- well something doesn't work any more.
I'm open to suggestions. I know we looked a difference in the javascript file ~ 2 years ago between the TDE version and openSUSE KDE3 version, and since that time kate-editor.org pulled the plug.
I would probably lean toward hooking the [Download] URL button to a git repository that could provide a more or less seamless URL change for where kate looks for the updates? Thoughts?
Hi David, Kate's syntax files are downloaded from our source code repository and it has been like that for 5 or 6 years now. - From time to time we update those files. We used to do that often when KAte 2.5 syntax files were still available. Now we need more work on those files. Probably the next update will be for R14.1.0 release. If you or any user wants to update the existing files and propose a patch for any update, feel free to do so and we will be happy to integrate that.
Cheers Michele
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 05/16/2020 10:23 AM, Michele Calgaro via trinity-devel wrote:
Hi David, Kate's syntax files are downloaded from our source code repository and it has been like that for 5 or 6 years now. From time to time we update those files. We used to do that often when KAte 2.5 syntax files were still available. Now we need more work on those files. Probably the next update will be for R14.1.0 release. If you or any user wants to update the existing files and propose a patch for any update, feel free to do so and we will be happy to integrate that.
Cheers Michele
Thanks Michele,
Only thing I have run into lately is the htlm and/or css syntax file that craters when it reaches:
@media screen and (max-height: 450px) { .sidenav {padding-top: 15px;} .sidenav a {font-size: 18px;} }
It does not recognize the enclosing (...) as a termination of the css property and value -- which crashes highlighting from that point on in the document. I don't do much web work, but the @media and e.g. screen or print, etc.. was a fairly recent addition (anything in the last 5-6 years is recent to me...)
I have looked at the xml file to attempt to sort out what needs to be added or changed -- but that is more than Greek to me. Who can help with this type issue?
On Sun, 17 May 2020 00:18:42 -0500 "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
Only thing I have run into lately is the htlm and/or css syntax file that craters when it reaches:
@media screen and (max-height: 450px) { .sidenav {padding-top: 15px;} .sidenav a {font-size: 18px;} }
It does not recognize the enclosing (...) as a termination of the css property and value -- which crashes highlighting from that point on in the document. I don't do much web work, but the @media and e.g. screen or print, etc.. was a fairly recent addition (anything in the last 5-6 years is recent to me...)
I have looked at the xml file to attempt to sort out what needs to be added or changed -- but that is more than Greek to me. Who can help with this type issue?
Interesting. Your fragment appears to highlight correctly for me (using Kate syntax highlighting XML files installed at the very end of 2017). Either there's been a regression, or the issue is something else in your CSS/HTML file.
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2020 Sun, 17 May 07:43:17 -0400 E. Liddell scripsit:
On Sun, 17 May 2020 00:18:42 -0500 "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
Only thing I have run into lately is the htlm and/or css syntax file that craters when it reaches:
@media screen and (max-height: 450px) { .sidenav {padding-top: 15px;} .sidenav a {font-size: 18px;} }
It does not recognize the enclosing (...) as a termination of the css property and value -- which crashes highlighting from that point on in the document. I don't do much web work, but the @media and e.g. screen or print, etc.. was a fairly recent addition (anything in the last 5-6 years is recent to me...)
I have looked at the xml file to attempt to sort out what needs to be added or changed -- but that is more than Greek to me. Who can help with this type issue?
Interesting. Your fragment appears to highlight correctly for me (using Kate syntax highlighting XML files installed at the very end of 2017). Either there's been a regression, or the issue is something else in your CSS/HTML file.
E. Liddell
Works here, too. I saved the fragment as a.css Nik
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
David C. Rankin -
Dr. Nikolaus Klepp -
E. Liddell -
Michele Calgaro via trinity-devel