mkn | Simple SSR Scaffolding for React Projects

You're getting the output with il, because the N -> NP instance of mkNP makes mass nouns. The canonical example is "I drink water", where water is constructed with mkNP water_N.

In some resource grammars, this mkNP instance creates NPs without any article: like English "I drink water". In other languages like French, it creates a NP in partitive: "je bois de l'eau". Italian gives, not the bare form like English, nor a partitive like French, but a normal definite article: "bevo l'acqua".

Why would the RGL creators do this? When writing an application grammar, the mkNP : N -> NP instance is a higher-level construct for mass noun, rather than a lower-level question of "do I put an article or not".

The downsides are that it's almost impossible to ever output a bare form in the languages where mkN : N -> NP adds an article. As far as I understand, it's possible only as a standalone utterance, see e.g. this answer on the GF mailing list.

A huge number of overloads is the intended way of doing things. Just look at any category in the RGL synopsis, you see easily over 20 overloads for a single function name. It may be annoying to define them, but that's something you only need to do once. Then when you use your overloads, it's much nicer to use them like this:

To get cc (short for compute_concrete) in the GF shell to print only one result, you can use the flag -one. Like this:

The purpose of N2 and N3 is nouns that take an argument. The example in the RGL documentation is "distance from this city to Paris".

Now, obviously you can say just "distance", it's not wrong. That's why we have functions that make N2 and N3 into a CN without arguments.

The converse is also true: you can say, as in it's not wrong to say, "the tree from Tokyo to Paris". Here's a silly context: "which trees are we sending to which places?" "this is the tree from Tokyo to Paris".

But, I hope that you agree, that the arguments from X and to Y feel a bit more natural for "distance" than for "tree". The line is blurry on purpose --- you as a grammarian can always decide whether it makes more sense to encode a preposition into the noun (make it into a N2/N3), or whether to attach full adverbial to a regular noun (N).

So let's see what happens in the N2 and CN.

Your general approach with using | is correct.

There is no empty determiner, but rather another overload instance of mkNP. There's one with a determiner (so Det -> N -> NP) and another without, just N -> NP. So you can do this:

As mentioned in the comments, your gnuplot script does not match your Matlab script in several definitions.

Especially in your case, I would strongly recommend to define arrays and functions. This will avoid copy paste mistakes and will make the code shorter and clearer. I hope you are working with gnuplot >=5.2, because the code below uses arrays.

I started from your Matlab script and cleaned it up a bit. Having a semicolon ; at the end of a line in gnuplot is not necessary, but it also doesn't harm. The power in Matlab ^ is ** in gnuplot. By the way, in your Matlab code I can't see where the variable Mn=33.705 is used. Furthermore, as mentioned in the comments, pay attention when using divisions in gnuplot, because gnuplot is using integer division if not one of the numbers is a float number. This is one of the meanest pitfalls in gnuplot getting unexpected results. For the colors you could also use RGB hexadecimal-numbers in the format 0xRRGGBB.

Code:

First of all, the structure you made isn't a relative clause, but this structure:

Like @aschepler said, "hosted by BBC" is a participle phrase, not passive voice. In the Extend module, there are a couple of functions to create participles from VPs:

Theoretically, the answer is no - you can't always remove the line breaks. This is simply because RFC 1421 defines situations in which you must include the line breaks:

Text lines, delimited by the character pair , must be no more than 1000 characters long.

The above statement is in Section 4.3 of RFC 1421, the document where the PEM format is defined.

Practically, however, the answer is generally yes: a number of common implementations are quite lenient when parsing objects in PEM format and allow for excessively long text lengths. Specifically, OpenSSL and the Golang PEM implementation allow this (or, at least lengths longer than 1000 characters).

Try running this command on one of your certificates with the line breaks removed - it succeeds: