Ambiguous FreeTextLiteral

Hello!
I have a problem with scanning of FreeTextLiteral.
That one was detected when input text starts with any character missing in hash table.
How to create Terminal which fits free text starts with any character (including latin characters).
Can anybody help me?

First, do you use this FreeTextLiteral in any of the rules? if not, you should add it to NonGrammarTerminals.

Otherwise, if it is used somewhere, then Scanner should find it. If it does not define any Firsts prefixes (GetFirsts() return null or empty list), it should be automatically added to FallbackTerminals. Step thru the process and check that this is so (stop
when scanner tries to find a terminal and check that your FreeTextTerminal is in the list of FallBackTerminals)

I want to see a free text in the parse tree so I haven't added FreeTextLiteral to NonGrammarTerminals.
And FreeTextTerminal is always in the list of FallBackTerminals.
I have to scan and parse a text like this:

It would be helpful next time if you provide a sample that you try to parse and also point to the exact place when parser reports an error.

But from what I see my guess would be that the trouble is in PORTFOLIO_EX definition - it should not have LINE_END in both clauses. Semicolon and linebreak are defined as terminators for FREE_TEXT elements and are consumed by this element - in the sense
that when parser completes reading FREE_TEXT, the current position of the scanner is at the beginning of the next line, after "\n". But parser still wants to see LINE_END, because it is specified in the rule.

So just try removing LINE_END from PORTFOLIO_EX rule. Let me know if it works. If it's not the problem, then please provide a sample and failure position

As you can see I add prefix for token. The prefix is '@'. And parsing works right. When free text starts with any char which can be start of terminal FIRM it doesn't work (
If i add a char to Firsts list of FreeTextLiteral it will work but when text starts with this char. But as I said I want free text can starts with any character (including latin).
It isn't good idea to add all latin chars to Firsts list, is it?
And more about parsing error. I try to parse text:

PORTFOLIO_EX The very long name of portfolio;DESCRIPTION Any description. You can write much here;FIRMS_LIST ALL_FIRMS;

I see the problem now. If you look at your first screenshot, in the right-bottom corner, you see token list. The second token produced by scanner is "FIRM" - an identifier token you defined for firms. It is Irony's inconsistency in dealing with
terminals without prefixes, long outstanding item. The trouble is Scanner.SelectTerminals method. No-prefix terminals are picked up for consideration ONLY if there are no other candidates with prefixes. In your case there is one candidate - "Firm"
identifier, so it leaves out the FREE_TEXT which is in FallbackTerminals. This is wrong, it should be fixed, I simply did not come up yet with consistent and reliable fix for this - this is actually more than a fix, it is sort of refactoring and change of
entire scanning algorithm. Until now this bug manifested itself in little inconsistencies but your case is blown up by this. Sorry, will get to this ASAP. For now, add all Latin upper and lower letters to Firsts list of FreeTextLiterals you use - yes, it looks
silly, and it would work only for English, but would work until the fix is there.