Download the PHP package markup-carve/carve-php without Composer
On this page you can find all versions of the php package markup-carve/carve-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download markup-carve/carve-php
More information about markup-carve/carve-php
Files in markup-carve/carve-php
Package carve-php
Short Description PHP parser for Carve, a human-centered lightweight markup language derived from Markdown and Djot.
License MIT
Homepage https://markup-carve.github.io/carve/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package carve-php
carve-php
PHP parser and renderer for Carve, a lightweight markup language for readable source and structured documents.
Implements Carve spec 0.1 (see Versioning & Changelog).
Installation
composer require markup-carve/carve-phpUsage
use MarkupCarve\Carve\CarveConverter;
$converter = new CarveConverter();
$html = $converter->convert('# Hello /Carve/');The HTML, Markdown, Djot and BBCode importers return a versioned
migration-fidelity report from each converter's convertWithFidelityReport()
method. One preserved / normalized / degraded / dropped vocabulary spans
all four, with format-specific diagnostic codes underneath. The report envelope
and the --check-loss gate are in docs/cli.md;
HTML also has a detailed import report, in docs/html-import.md.
Besides HTML the converter renders Markdown, plain text and ANSI. The Markdown writer's options are in docs/markdown-output.md, and every node can carry its source line - docs/source-lines.md.
A document can pull in other files with {{ chapter.crv }}. It is opt-in and
off by default - the core parser performs no file I/O - and the resolver you
supply is the security boundary: docs/includes.md.
Source-aware tools can prepare stale-safe structured formatting changes through
CarveConverter::toCarvePatch(); see the
source-preserving patch guide.
CLI
vendor/bin/carve README.crv > README.html # render (HTML by default)
vendor/bin/carve --markdown README.crv # or --plain, --ansi, --json
vendor/bin/carve lint README.crv # report problems, change nothing
vendor/bin/carve migrate --from html p.html # convert into CarveEvery subcommand and flag is in docs/cli.md.
Sandbox
Try this implementation live in the Carve sandbox - explore syntax and extensions, inspect output, and share snippets via pastebin-style links. It also powers the wp-carve WordPress plugin.
ProseMirror / Tiptap
The AST converts to a ProseMirror document and back, so a Tiptap editor in the browser and PHP rendering on the server share one source of truth with no Node runtime. See docs/prosemirror.md.
Untrusted input
Rendering attacker-controlled Carve needs the safe path, which escapes raw HTML instead of emitting it and bounds nesting depth. The threat model, the defaults and the full checklist are in docs/security.md.
Linting
carve lint reports constructs that parse but render differently from what
the author intended. The rules and options are in docs/lint.md.
Documentation
- Importing HTML - the loss report and the diagnostic path locator.
- Extensions - the extension set, and writing a parse-stage matcher.
- Command line - every subcommand and flag.
- Untrusted input - the threat model and the safe path.
- Linting - the lint rules and options.
- Markdown output - the Markdown writer's options.
- Source-line tracking - carrying source positions on the AST.
- Source-preserving patches - stale-safe UTF-8 edits.
- Stored documents - spec versions and stored content.
- ProseMirror / Tiptap - editor interchange.
- AST JSON - the interchange format.
- Integrated definition layout - collecting and resolving reference, footnote and abbreviation definitions.
- Configured conversion fast path - reusing a configured converter.
Development
Local setup, the test suites, the style and static-analysis gates, and the rules for a spec-affecting change are in CONTRIBUTING.md.
