Figured I'd throw in what it'd look like if retext supported async parsing middleware. One ability of parsing asynchronously is to query external datasets against words or phases during parsing. By using ware, we can also abstract the logic of supporting various async flows.

Initial checklist

• [X] I read the support docs
• [X] I read the contributing guide
• [X] I agree to follow the code of conduct
• [X] I searched issues and couldn’t find anything (or linked relevant results below)

Problem

error: Import 'https://cdn.esm.sh/v57/[email protected]/es2021/nlcst-to-string.js' failed: 408 Request Timeout at https://cdn.esm.sh/v57/[email protected]/es2021/parse-latin.js:2:27264

Deosn't seem to work with Deno yet.

Solution

support Deno

Alternatives

https://esm.sh

The following code executes as expected, reporting issues of the given text.

                retext().use(readability).process(processedReview.text, function (err, file) {
                        console.log(report(file));
                });

However this one reports 'no issues found' for the exact same text. Am I missing some JS basics here? ATM I am really stuck, thank you for your help.

                var process = retext().use(readability).process;
                process(processedReview.text, function (err, file) {
                        console.log(report(file));
                });

If I use the example at https://github.com/wooorm/retext#usage, I get the error

C:\Users\Morten\node_modules\retext-emoji\index.js:133
    var proto = processor.Parser.prototype;
                                ^

TypeError: Cannot read property 'prototype' of undefined
    at emoji (C:\Users\Morten\node_modules\retext-emoji\index.js:133:33)
    at Retext.use (C:\Users\Morten\node_modules\retext\index.js:113:19)
    at Object.<anonymous> (C:\Users\Morten\Desktop\retext.js:8:6)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:475:10)
    at startup (node.js:117:18)
    at node.js:951:3

I have installed retext, retext-emoji and retext-smartypants and I'm using node v4.0.0.

Initial checklist

• [x] I read the support docs
• [x] I read the contributing guide
• [x] I agree to follow the code of conduct
• [x] I searched issues and couldn’t find anything (or linked relevant results below)
• [x] If applicable, I’ve added docs and tests

Description of changes

Repository

A retext plugin for checking popular names casing.

Examples:

• ⚠️ macbook → ✅ MacBook
• ⚠️ MacOS → ✅ macOS

For:

• Abbreviates
• Brands
• General
• Products
• Softwares

Dictionaries are from case-police.

First of all, awesome and really well done project. Congrats!

Is it only for English? I mean, I saw that it supports latin chars, but would it work for say, separating syllables, or finding phonetics / rhymes in portuguese text?

Thank you!!

I made this plugin for checking for cliches.

Any thoughts about it would be cool!

Might want to hold off merging in until I can figure out how to get my travis test to pass on every version node though.

Cheers

I've tried multiple times to install this via Bower but it seems to hang in the same spot every single time. Tried cleaning cache but all attempts end in the same result. This is the line where it hangs:

bower resolved      git://github.com/wooorm/array-iterate.git#0.1.0

Subject of the issue

I stumbled upon a strange case where retext fails to detect some sentences ending with number (but not all).

Your environment

• OS: Windows & Linux
• Packages: retext, unist-util-visit, nlcst-to-string

Steps to reproduce

I try to parse the following string "Hello 30. Hello world."

const retext = require('retext');
const visit = require('unist-util-visit');
const toString = require('nlcst-to-string');

var str = 'Hello 30. Hello world.'

const tree = retext.parse(str);

visit(tree, 'SentenceNode', (node)=>{
    console.log('>', toString(node));
} );

Expected behaviour

output :

> Hello 30.
> Hello world.

Actual behaviour

output :

> Hello 30. Hello world.

Please note that if I test the same code with this string "Hello 3030. Hello world." , it works just fine.

it seems to happen with numbers with less than four digits .

Hello,

thanks for retext — it is very elegant to use! Although I have managed to create a plugin which filters a tree, it seems the next plugin in the chain does not inherit of the changes of the previous plugin.

Here is my high level code:

      retext()
        .use(retextStopwords, { stopwords: stopwordsFr })
        .use(retextKeywords)
        .process(text, (err, file) => {
            if (err) {
            return reject(err);
          }

          resolve({
            keywords: file.namespace('retext').keywords,
            keyphrases: file.namespace('retext').keyphrases
          });
        });

retextKeywords is the retext-keywords plugin but because it does not catch french stopwords, I ought to modify the tree to remove them. Here is the code of retextStopwords:

'use strict';

const filter = require('unist-util-filter');

module.exports = (retext, options) => {
  const stopwords = options.stopwords;

  return (node, file, next) => {
    const tree = filter(node, node => {
      return !(node.type === 'TextNode' && stopwords.indexOf(node.value) > -1);
    });

    file.namespace('retext').tree = tree;

    next(null, tree, file);
  };
};

When I check tree, it indeed does not contain the TextNodes I wanted to remove. But these words are still taken in account by retextKeywords which is next in the use() chain.

Any tip or hint to perform this?

Thanks a lot :-)

When running bower install retext-keywords, I get the error ENOTFOUND Package retext-keywords not found. I would also appreciate some help on getting retext-keywords running on the client-side as per the demo.

Initial checklist

• [x] I read the support docs
• [x] I read the contributing guide
• [x] I agree to follow the code of conduct
• [x] I searched issues and couldn’t find anything (or linked relevant results below)
• [x] If applicable, I’ve added docs and tests

Description of changes

This updates parse-latin, parse-english, parse-dutch, to versions that include types. And clean their APIs. This is a major as it will break several plugins as of now. They will need updating.

Continuation of https://spectrum.chat/?t=16557712-7029-4718-a2bc-38453fdfb928 and https://github.com/unifiedjs/governance/issues/11 @aecepoglu is offering to contribute retext-language-server. https://github.com/unifiedjs/governance/blob/master/governance-grant.md

I think it could be a good fit for the organization, and a good starting point for additional language servers for other unified projects. Thoughts @retextjs/core?