Comments (12)
I wonder whether this wants to be a http://wiki.languagetool.org/ sub-page where the rule is explained, limitations are listed and the grammar/spelling rule is referenced with reputable sites.
from languagetool.
Well, we haven't documented the rules in such detail because they are usually improved over the years and writing docs is also time-consuming. I think external references are enough. However, we could host explanations of rules -- including these links -- but it's then a major effort to maintain them.
from languagetool.
The rules in the Dutch grammar.xml are well documented with urls to reputable sites. :)
Here is a proposal to make it easier to review urls in grammar.xml files. Create an XSL that allows the XML to be rendered in a web browser (directly or after XSLT) showing:
- name or abbreviation of the language
- datetime of the last edit
- categories with at least name
- rulegroups with at least id, name and clickable url
- rules with at least id, name, messages and clickable url
Upon each change of a grammar.xml file, this HTML page should automatically get regenerated. This can be part of https://languagetool.org/development/
This is especially handy for editorial people that do not have programming skills or are lost in XML and by this is a way to get them more involved in LanguageTool. I know people who would like to review urls and add propose new ones (to a developer) but at the moment it is too difficult for them to do that on their own.
Original reason why I found this issue is the following. I would like to change the grammar.xsd to allow for more than one url per rule and rulegroup. Can somebody check if this has no negative side effects for LT? If there are none, I will have some pull requests (one for the XSD and one for Dutch grammar.xml with addtional urls). The rationale is that the Dutch language authority itself has multiple pages per rule or advice.
from languagetool.
Just changing grammar.xsd
to allow more than one URL will (probably) not work, the Java code needs to be adapted, too. We haven't done that yet as we prefer to give exactly one URL, it's easier for the user. If they want more opinions, they can always google anyway. Aren't the pages of the Dutch language authority linked, or don't they have some logical order?
from languagetool.
There are multiple sources. I once suggested to add data to the opentaal site with one page per rule, showing some text and maybe some sources.
Op 17 sep. 2015 10:34 schreef Daniel Naber [email protected]:Just changing grammar.xsd to allow more than one URL will (probably) not work, the Java code needs to be adapted, too. We haven't done that yet as we prefer to give exactly one URL, it's easier for the user. If they want more opinions, they can always google anyway. Aren't the pages of the Dutch language authority linked, or don't they have some logical order?
—Reply to this email directly or view it on GitHub.
from languagetool.
At the moment there are links to OnzeTaal which is nog the Dutch language authority (Taalunie) but it has very important information. The pages in both OnzeTaal and Taalunie have links themselves to other relevant pages on their website. So it is not that we want to add all these pages but for each source we would like to add at least one page.
In stead of one link, that would be maximum two or three links. It is better not to do this on the site of OpenTaal as it would introduce an extra dependency and and extra place to manage the links.
@danielnaber, if you point out where the urls are processed I would like to help out making the offering of more than one url possible. As an intermediate step, if the XSD would allow it in the XML, at least the current implementation should still work with only one url.
from languagetool.
In line 2 of grammar.xml, there is a reference to a stylesheet called
print.xsl
(~\languagetool-core\src\main\resources\org\languagetool\rules\print.xsl).
It should enable users to open grammar.xml in a browser and display the
rules in a way that is much easier to read, with URLs transformed into
clickable links, wrong examples in red, replacements in green, and
correct examples in gray. For some reason, though, it only works in
Internet Explorer for me.
--Jan
Am 17.09.2015 10:14, schrieb Pander:
The rules in the Dutch grammar.xml are well documented with urls to
reputable sites. :)Here is a proposal to make it easier to review urls in grammar.xml
files. Create an XSL that allows the XML to be rendered in a web browser
(directly or after XSLT) showing:
- name or abbreviation of the language
- datetime of the last edit
- categories with at least name
- rulegroups with at least id, name and clickable url
- rules with at least id, name, messages and clickable url
Upon each change of a grammar.xml file, this HTML page should
automatically get regenerated. This can be part of
https://languagetool.org/development/This is especially handy for editorial people that do not have
programming skills or are lost in XML and by this is a way to get them
more involved in LanguageTool. I know people who would like to review
urls and add propose new ones (to a developer) but at the moment it is
too difficult for them to do that on their own.Original reason why I found this issue is the following. I would like to
change the grammar.xsd to allow for more than one url per rule and
rulegroup. Can somebody check if this has no negative side effects for
LT? If there are none, I will have some pull requests (one for the XSD
and one for Dutch grammar.xml with addtional urls). The rationale is
that the Dutch language authority itself has multiple pages per rule or
advice.—
Reply to this email directly or view it on GitHub
#12 (comment).
from languagetool.
The url parsing code is here: https://github.com/languagetool-org/languagetool/blob/master/languagetool-core/src/main/java/org/languagetool/rules/patterns/PatternRuleHandler.java#L111
from languagetool.
See #312
from languagetool.
Hallo,
Could I ask what are you looking for nowadays? Adding more than a URL per rule, showing them in a specifical way (where?)... Please give me more information for trying to enhance it.
from languagetool.
Hi @davidemdot, adding more than one rule should rarely be needed. From my point of view, the task is to make sure there is a URL if the rule actually needs more explanation.
from languagetool.
Ok, thanks. So I will take it into account when I add new rules, and also I will check if there is any missing URL in the Spanish grammar.
from languagetool.
Related Issues (20)
- [en] For British English, the LT spell checker does not find upper-case CENTER, but it finds lower-case HOT 12
- [pt-PT] Importing entities — 2024-07-11 HOT 4
- can't use custom server in word add-in
- [de] No detection for swapped wo/so
- [de] false positive for Getrenntschreibung in "und los ging’s" HOT 1
- [en] AmE, spelling loop for decafarad > dekafarad HOT 3
- LanguageTool not able to detect errors in this text HOT 1
- [DE] Prof. assumed to be masculine
- BlueprintJS EditableText component breaks unexpectedly
- [en] replace.txt for British/American words HOT 2
- [DE] Fehlalarm mit "kein Danke"
- Argyle-Muster und Schurwollqualität
- detect_screen() for "install.sh -c GUI" ?
- [FR] Making proper release on github?
- What to do if not working in a specific editor? HOT 4
- Vaadin Message Input Fields vanish on click
- [en] a/an false positives HOT 1
- [en] unexpected Checkout splitting suggestion on a proper name HOT 1
- [en] "If string" past participle false positive in a programming parameter documentation description
- [DE] Fehlalarm mit "Tag über zu begleiten"
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from languagetool.