Skip to content

Commit a01d172

Browse files
committed
Update project status in Readme now that PEG grammar is complete
1 parent d62e5b7 commit a01d172

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ Other implementations already exist in [Rust][fluent-rs], [Javascript][fluent.js
1414

1515
## Status
1616

17-
As of yet this does nothing useful; the code base is mostly boiler plate to get the Lua project started with a touch of experimentation thrown in for good measure. I'm actively soliciting feedback on how the API should look and work in Lua from several projects that might use it. If this is of interest to you please join the project chat and/or open [issues](https://github.com/alerque/fluent-lua/issues) for points of discussion.
17+
As of yet this does nothing *usable* (see [lua alternatives][#alternatives]). I'm actively soliciting feedback on how the API should look and work in Lua from several projects that might use it. If this is of interest to you please join the project chat and/or open [issues](https://github.com/alerque/fluent-lua/issues) for points of discussion.
18+
19+
**Update 2019-09-14**: I've completed a PEG grammar based parser for the entire 1.0 Fluent file format spec. All the pieces are there, but it's only partially tested. It at least parses a few basic types of entries. The AST it returns is straight out of *luaebnf* and probably needs massaging to match the reference ones (via capture groups?), then it needs testing against the upstream fixtures.
1820

1921
## Alternative(s)
2022

0 commit comments

Comments
 (0)