🚀
Codex Editor
  • Project Overview
    • Welcome to Codex
    • Codex Editor
      • Features
      • What was Project Accelerate?
        • Project Philosophy
        • Steering Committee
    • Vision
      • Powerful Tools and Simplicity
      • Streamlining the Translation Process
      • Unopinionated Assistance
    • Architecture
    • Frequently Asked Questions
    • Translator Requirements
    • Roadmap
    • Why VS Code?
    • Multimodality
  • Translator's Copilot
    • What is Translator's Copilot?
    • Information Management
      • Resource Indexing
      • Greek/Hebrew Insights
      • Chat with Resources
      • Project-Based Insights
    • Translation Assistance
      • Translation Drafting
        • Prioritizing Semantics over Structures
        • Reranked Translation Suggestions
      • Quality Checking
        • Token matching evaluation
        • Few-shot evaluation
        • Fine-tuned Bible QA model
        • Character and word n-gram evaluation
        • Simulated GAN evaluation
        • Linguistic Anomaly Detection (LAD)
      • Back Translation
    • Orchestration
      • Translation Memory
      • Multi-Agent Simulations
      • Drafting linguistic resources
    • Intelligent Functions Library
  • Development
    • Codex Basics
      • Projects
      • The Editor
      • Extensions
        • Rendered Views
        • Language Servers
        • Custom Notebooks
        • Global State
    • Experimental Repositories
Powered by GitBook
On this page
  1. Development
  2. Codex Basics

The Editor

PreviousProjectsNextExtensions

Last updated 1 year ago

The core feature of VS Code is its editor. This editor allows you to work on text documents in virtually any format.

Considerations

There are a couple of considerations here:

  1. Users want a WYSIWYG editor

  2. Users want an editor that doesn't annoy them too much

To solve the first problem, we have simply added a code lends button to render the notebook content as something that looks more like a Bible. You can add whitespace structure too, by adding additional blank lines between content. This allows users to structure poetry, quotations, etc., without use of markers.

We also allow ranges of verse references in two different ways:

  1. If you put multiple verse references right next to each other, e.g., GEN 1:1 GEN 1:2, then they will be rendered as 1-2.

  2. If you leave a verse blank and instead of content put a range marker (<range>), it will be treated as part of the most recent non-range verse.