pseudocode-i18n-languageserver

Current version: 0.9.6. Release history: pseudocode-i18n-languageserver changelog. pseudocode-i18n-languageserver gives .pseudo and .algo files one reusable intelligence layer for open-source editors and educational IDEs. The server speaks the standard Language Server Protocol (LSP) over stdin/stdout and delegates the language itself to pseudocode-i18n.

Install it once:

python -m pip install 'pseudocode-i18n-languageserver>=0.9.6,<0.10'

On an externally managed Python installation, when you deliberately install into user/system packages:

python -m pip install --break-system-packages 'pseudocode-i18n-languageserver>=0.9.6,<0.10'

Check the command used by editors:

pseudo-lsp --version

You normally do not launch pseudo-lsp yourself. Kate, Neovim, Spyder or another LSP client starts it as a child process and communicates with it through stdin/stdout.

Shared editor intelligence

pseudo-lsp exposes the coordinated editor contract while keeping the language itself in pseudocode-i18n:

• multiple localized diagnostics from the recovering core linter, with exact source ranges;
• completion plus retained frontend snippets, signature help, document symbols, definitions, references, rename and formatting;
• hover documentation generated by the core for ordinary keywords and structural grammar fragments such as Alors, fois, Jusqu'à ce que and every word of localized multi-word import aliases such as en tant que;
• import operands remain symbols rather than documentation keywords, preventing false hover/help on names such as an imported sqrt;
• all 14 source languages receive the same behavior without maintaining language-specific tables in the server;
• project-aware standard/local module resolution and strict type/operation diagnostics are preserved;
• pseudocode/tutor exposes the shared pseudocode-tutor/v1 step-by-step execution model;
• pseudocode/flowchart exposes the shared Mermaid model, including symbol scope, theme and active execution line/condition for synchronized Tutor views.
• custom Pseudocode requests share one document-parameter normalizer, accepting standard textDocument.uri plus compatibility fallbacks without duplicating parsing in editor plugins.

The server remains a thin LSP layer: source-language knowledge belongs to pseudocode-i18n, so VS Code, Thonny and other clients see the same diagnostics and help.

Language-server capabilities

The server exposes the same language intelligence for all 14 supported natural languages:

• diagnostics from the native pseudocode-i18n parser and semantic linter, including multiple independent errors in one document, explicit type-contract mismatches and incompatible typed operations;
• project-aware module diagnostics: math and random are standard, while existing local .pseudo / .algo modules are resolved from the document/project path;
• i18n code completion and the existing structural snippets, using the normal language-resolution priority;
• completion for document symbols, localized built-ins, constants and types;
• pedagogical hover information for symbols, keywords, types and built-ins, with localized section labels and every accepted syntax synonym exposed;
• signature help;
• document symbols;
• go to definition;
• find references;
• prepare rename and rename;
• whole-document formatting;
• .pseudo and .algo as equivalent source extensions.

The server does not maintain a second grammar. pseudocode-i18n remains the source of truth for parsing, language detection, configuration, formatting, diagnostics, snippets and semantic indexing.

Language and snippet resolution

A document uses the same precedence as the core:

1. explicit # language: xx / # lang: xx directive;
2. language: / lang: in pseudocode.config.yml;
3. automatic language detection;
4. fallback_language;
5. French as the final default.

This means typing a condition snippet in a French file proposes Si … Alors, while an English file proposes If … Then, without editor-specific copies of the snippet catalog.

Editor targets

See the Editors section of the documentation for exact configuration and current limitations.

Development

yarn setup
yarn bfc

yarn setup installs the current project and uses a sibling ../pseudocode-i18n checkout when present. yarn bfc is an alias for yarn build:full:check and performs version synchronization, generated integrations, linting, tests, a CLI smoke test, strict MkDocs documentation build and Python package build.

Useful commands:

yarn dev
yarn dev:lan
yarn test
yarn lint
yarn smoke
yarn zip

License

GNU General Public License version 3 or later (GPL-3.0-or-later).