Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
On Sun, Apr 15, 2018 at 12:49:05AM +0100, Lajos Veres wrote: > * Package name: misspell-fixer > Description : Tool for fixing common misspellings, typos in source code. [...] > Reason: > I have not found any sourcecode typofixer tool in Debian. > Some users also mentioned that their life would be a little easier with a > packaged version. This sounds awfully similar to the package named codespell. -- Met vriendelijke groet / with kind regards, Guus Sliepen signature.asc Description: PGP signature
Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
On Sun, Apr 15, 2018 at 11:53:15AM +0100, Lajos Veres wrote: > On Sun, 15 Apr 2018, kact...@gnu.org wrote: > > > [2018-04-15 00:49] Lajos Veres > > > [...] > > > > > > --- > > > > > > Reason: I have not found any sourcecode typofixer tool in Debian. > > > Some users also mentioned that their life would be a little easier > > > with a packaged version. > > > > Lintian supports some spell checking, including 'spelling error in > > binary'. Maybe their power could be united? > > That sounds a great idea. > Could you please help me to understand the scale of it and its potential > requirements, subtasks? Just to note that there is also the codespell tool, also available in Debian as a package. However, both Lintian and codespell only try to detect misspellings, not fix them. In Lintian's case this is kind of obvious - it is supposed to operate on the result of a build (even if source-only), so it cannot really figure out where the source of the misspelling is. For codespell I wonder if the author didn't try to include any fixing functionality for at least one major reason: some of the misspellings it detects are false positives, sometimes these are real words, or variable or function names, or domain-specific terms, or even (at least for the hexer and stunnel4 packages that I help maintain) actual words *in another language* :) So, hm, it may be nice to have a tool that also corrects misspelled words, but IMHO it should either be interactive or, at the very least, support some kind of per-project whitelist of words that it should not really try to correct. In any case, thanks for trying to make Debian better, whatever direction this happens to go into! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
On Sun, 15 Apr 2018 11:35:11 +0100 (BST) Lajos Veres wrote: > (I am not very familiar with Debian packaging. So sorry if I missed any > rules/etc.) The first one you should be aware of is that bug submitters and random folks commenting on a bug are not subscribed to the bug by default. So you should CC bugs submitters and anyone who replies to bugs. For the rest, check out this page if you haven't yet: https://mentors.debian.net/intro-maintainers > Anyway I think it would be a good idea to offer more options to the users. > The tools use a different dictionaries, they perform differently in > different environments and their features sets are not exactly the same > either. Agreed. > Generally I would be happy to do the "grunt work". > Just I think I would need a few pointers. Great, start with the page above. > I tried to prepare the debian folder, but I assume it may have some > bugs/inconsistencies. To start with, please check your .changes file using lintian: https://lintian.debian.org/ You might also want to run check-all-the-things against the code: https://github.com/collab-qa/check-all-the-things/ > At the moment the project does not really have a mature versioning policy > either, but I am happy to introduce something, just not too sure which one > would be the best. That is completely up to you, but semver is a popular one: https://semver.org/ > And probably a few other similar questions. (At least what I am aware of. > :-) ) Feel free to ask packaging questions on the mentors list or irc channel: https://lists.debian.org/debian-mentors/ https://ircs.debian.org/debian-mentors PS: check-all-the-things includes several checkers of English spelling, grammar and prose. It could also support your misspell-fixer tool: https://github.com/collab-qa/check-all-the-things/blob/master/data/english.ini -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
On Sun, 15 Apr 2018, kact...@gnu.org wrote: > [2018-04-15 00:49] Lajos Veres > > [...] > > > > --- > > > > Reason: I have not found any sourcecode typofixer tool in Debian. > > Some users also mentioned that their life would be a little easier > > with a packaged version. > > Lintian supports some spell checking, including 'spelling error in > binary'. Maybe their power could be united? That sounds a great idea. Could you please help me to understand the scale of it and its potential requirements, subtasks? -- Lajos Veres vla...@gmail.com 07927 460 778
Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
On Sun, 15 Apr 2018, Paul Wise wrote: > On Sun, 15 Apr 2018 00:49:05 +0100 Lajos Veres wrote: > > > I have not found any sourcecode typofixer tool in Debian. > > codespell -w > spellintian (doesn't autofix) > > Some more that are not yet in Debian: > > https://jwilk.net/software/mwic > https://jwilk.net/software/anorack > https://github.com/client9/misspell > https://github.com/lyda/misspell-check Thank you for your reply. (I am not very familiar with Debian packaging. So sorry if I missed any rules/etc.) It seems that I was not thorough enough with that search... Anyway I think it would be a good idea to offer more options to the users. The tools use a different dictionaries, they perform differently in different environments and their features sets are not exactly the same either. Generally I would be happy to do the "grunt work". Just I think I would need a few pointers. I tried to prepare the debian folder, but I assume it may have some bugs/inconsistencies. At the moment the project does not really have a mature versioning policy either, but I am happy to introduce something, just not too sure which one would be the best. And probably a few other similar questions. (At least what I am aware of. :-) ) Thank you. Best regards, -- Lajos Veres vla...@gmail.com 07927 460 778
Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
[2018-04-15 00:49] Lajos Veres > [...] > > --- > > Reason: I have not found any sourcecode typofixer tool in Debian. > Some users also mentioned that their life would be a little easier > with a packaged version. Lintian supports some spell checking, including 'spelling error in binary'. Maybe their power could be united? pgpGFU4qOrUmT.pgp Description: PGP signature
Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
On Sun, 15 Apr 2018 00:49:05 +0100 Lajos Veres wrote: > I have not found any sourcecode typofixer tool in Debian. codespell -w spellintian (doesn't autofix) Some more that are not yet in Debian: https://jwilk.net/software/mwic https://jwilk.net/software/anorack https://github.com/client9/misspell https://github.com/lyda/misspell-check -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.
Package: wnpp Severity: wishlist Owner: Lajos Veres * Package name: misspell-fixer Version : 2018.04.15 Upstream Author : Lajos Veres * URL : https://github.com/vlajos/misspell-fixer * License : BSD Programming Lang: Bash Description : Tool for fixing common misspellings, typos in source code. Utility to fix common misspellings, typos in source code. There are lots of typical misspellings in program code. Typically they are more eye-catching in the living code but they can easily hide in comments, examples, samples, notes and documentation. With this utility you can fix a large number of them very quickly. --- Reason: I have not found any sourcecode typofixer tool in Debian. Some users also mentioned that their life would be a little easier with a packaged version.
