pltxt2htm

This repository is a sub-project of Physics-Lab-Web

This project aimed to provide a translater that compiles the Quantam-PhysicsLab's text to html (with markdown, minor html tags and latex support as much as possible).

This project requires at least C++23, disables rtti and exceptions, use header-only style to supply api, has great cross platform ability and I strongly recommend you to use clang.

How to use?

You can use pltxt2htm in console, browser, python and c.

C++ APIs is in include/pltxt2htm, here is a simple example:

// example.cc
#include <fast_io/fast_io.h> // in include/fast_io
#include <pltxt2htm/pltxt2htm.hh> // in include/pltxt2htm

int main() {
    auto html = ::pltxt2htm::pltxt2advanced_html(u8R"(
# Hello Quantum PhysicsLab
With Markdown supports
)", u8"localhost:5173");
    ::fast_io::io::println(::fast_io::u8c_stdout(), html);

    return 0;
}

Compile it: (Windows)

clang++ example.cc -o example -std=c++23 -I include -lntdll

Other platforms:

clang++ example.cc -o example -std=c++23 -I include

And I strongly suggest you to add -O2, -fno-ident, -fno-exceptions, -fno-rtti, -fno-unwind-tables, -fno-asynchronous-unwind-tables, -DNDEBUG, -fuse-ld=lld, -flto=thin, -stdlib=libc++, -rtlib=compiler-rt, --unwindlib=libunwind and cross compiling flags(--target=$TRIPLET and --sysroot=$YOUR_SYSROOT_PATH) to your clang.

C++20 module example is in module/example.cc

Exported API

• pltxt2htm::parse_pltxt: Get AST of Quantum-Physics's text
  • only exported in C++ API (include/pltxt2htm/pltxt2htm.hh)
  • All the AST node is exported in C++ API (class derived from pltxt2htm::PlTxtNode)
• pltxt2htm::pltxt2advanced_html: Render for Experiment's introduction text, all Quantum-Physics's Tag, minor HTML tag, most of the markdown and latex syntax is supported.
  • only exported in C++ API (include/pltxt2htm/pltxt2htm.hh)
• pltxt2htm::pltxt2fixedadv_html: Does not escaping < to <, and the rest is the same as pltxt2htm::pltxt2advanced_html
• pltxt2htm::advanced_parser: C-Style pointer interface wrapper for pltxt2advanced_html
  • in include/pltxt2htm/pltxt2htm.h
  • Python API: pltxt2htm.advanced_parser(text: str, host: str) -> str
  • WASM API: _advanced_parser(text: string, host: string) -> string
• pltxt2htm::pltxt2common_html: Render for Experiment's title, very few syntax is enabled.
  • only exported in C++ API (include/pltxt2htm/pltxt2htm.hh)
• pltxt2htm::common_parser: C-Style pointer interface wrapper for pltxt2common_html
  • in include/pltxt2htm/pltxt2htm.h
  • Python API: pltxt2htm.common_parser(text: str) -> str
  • WASM API: _common_parser(text: string) -> string
• pltxt2htm::fixedadv_parser: C-Style pointer interface wrapper for pltxt2fixedadv_html
• version
  • C++ API: pltxt2htm::version::(major|minor|patch): Get version of pltxt2htm
  • Python API: pltxt2htm.__version__
  • WASM API: _ver_major() -> number, _ver_minor() -> number, _ver_patch() -> number

All C++ APIs have been listed in pltxt2htm.cppm

features

I am ensure any new features (like markdown extension) will break old Quantum Physics's text. However, compatibility is not the reason that we should stop our steps. Here are some features why I (or why I not) support:

markdown extension based on commonmark

• carriage return will be regarded as line break (unlike markdown, which requires 2 spaces before a carriage return to be considered a line break)
• HTML's br tag is supported (<br>, <BR>, <br/>, <br   >, <br   /> will be regarded as line break)
• Quantum-Physics's color tag is supported
• Quantum-Physics's a tag is supported
• Quantum-Physics's Discussion tag is supported
• Quantum-Physics's Experiment tag is supported
• Quantum-Physics's user tag is supported
• Quantum-Physics's size tag is supported
• Quantum-Physics&HTML's i tag is supported
• Quantum-Physics&HTML's b tag is supported
• HTML's <h1> tag is supported
• HTML's <h2> tag is supported
• HTML's <h3> tag is supported
• HTML's <h4> tag is supported
• HTML's <h5> tag is supported
• HTML's <h6> tag is supported
• HTML's <p> tag is supported
• HTML's <del> tag is supported
• HTML's <hr> tag is supported
• most of the markdown ATX headers are supported
  • commonmark example 69 ~ 76 does not support
• MarkDown escape characters are supported
• Indent code block does not support because I hate it.
• Markdown escape characters (ASCII punctuation character) are supported

Note: undocumented/untested features is undefined behavior

distribution

cmd/, wasm/ and py/ distributions share the same version of pltxt2htm::version

pltxt2htm only maintains the trunk, and the release versions are only snapshots.

For linux users, please compile and install pltxt2htm (and I will never provide binaries for linux since there are tons of linux triplets caused by glibc, musl and architectures)

others

Q: Is this the time to use C++20 module?

A: Not exactly. Despite clang, gcc and msvc all support C++20 modules, but the compiler crashes more frequently than hearder-only. At the same time, Header unit is not fullly supported.

Q: Why not use NDEBUG macro in include/pltxt2htm

A: Conditional compilation in function body will cause ODR violation and C++26 Contracts has the same problem. therefore, to make function has different symbols in debug / release mode, I use template<bool ndebug> to achieve it.