Project

General

Profile

Bug #7856

Improve parsing of specifications from ini files

Added by Alexandru Lungu 7 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version:

History

#1 Updated by Alexandru Lungu 7 months ago

Work in #7784 improved the parsing of font specifications such that spaces are also treated as separators (along with commas).
There is further work:
  • Don't crash if the font specification is not properly formatted. Fall-back to the default font (?) just like 4GL does. Eventually log that the font specification was not properly parsed.
  • Do an extensive testing on what other characters are considered delimiters (e.g semi-colon, dot, comma, colon, question-mark, etc.). Maybe commas and other characters are irrelevant and should be preprocessed out from the specification.
  • Test size phrase better. Is size = 10 the only valid specification? Can we use other symbols in between size and 10, beside or together with =?
  • Optional: move to a grammar based parsing of ini files. Currently, they are tokenized using split.

Also available in: Atom PDF