Eno ·
Follow 2020 development of the new reference parser at the blog

Eno · Notation For Users

author: Jane Doe
email: jane@eno-lang.org

-- my_content
Multi-line embedded content (e.g. markdown) here ...
-- my_content

active = #fff
hover = #b6b6b6

# cities
Den Haag: 52.069961, 4.302315
Málaga: 36.721447, -4.421291
서울특별시: 37.566984, 126.977041

# cities expanded < cities
Springfield: 38.790312, -77.186418

Eno is a user-centric data language. Its simple syntax and versatile nature serves a wide audience, both in regards to cultural background as well as technical ability. Unlike traditional developer- and machine-centric data languages, its type-agnostic design acknowledges the human ability to understand and use context and puts long-lasting user productivity before short-lived developer convenience.

Plugins · Highlighting And Extras

Libraries · Application Development

Libraries Addendum · Benchmarks, Playground, Types

History · The Journey So Far

The first draft for what is now known as eno notation was sketched out in early 2018 during R&D on a large publishing project around file-based content. It was designed and developed by Simon Repp, and still is to this day. Many contributions were made by people who have offered their cultural, technical and personal insight, reported bugs and submitted code and corrections and set out to develop their own libraries for eno notation - I'd like to hereby express my gratitude to all of you, thank you for being part of this adventure.

Present And Future · The Road Ahead

As of early summer 2020 major efforts are made to enable eno notation usage in native development (C, C++, Go, Rust, et al). Therein the development of a new C-based reference parsing library will serve as a vehicle for clearly specifying and thereby resolving the last remaining ambiguities in the specification.

Building on top of the new reference parser, research on a native and cross-platform parsing code generator is planned for the near future, enabling developers to obtain fully functional data serialization code for multiple languages based on a schema language that is to be defined in the process.

The mid and long term vision is to endeavour for standardization of eno notation either by institutional backing or through establishment of a de-facto standard through the power of community. If you sympathize with this vision, I invite you to the join into our endeavour and help make it happen.

For the latest developments you can subscribe to the blog.

Contact · Issues And Questions

For concrete technical issues or questions feel free to open issues in the respective repositories. To get in touch directly, write a mail to simon@fdpl.io or reach out through the fediverse at @freebliss@post.lurk.org.