Markdown editor questions
How does live Markdown editing work?
You type in the formatted document. Move the caret into bold or italic text to reveal that span’s editable delimiters; move away and it renders normally. Editing the markers changes the formatting and saved Markdown. Select text for a nearby formatting toolbar that keeps the exact editor selection. Escape dismisses it without clearing the selection; selecting again brings it back. Bullets and scalable task checkboxes inherit the chosen style: Normal/Formal use navy, while Kagantic uses blue accents and hard offsets. Reading mode is separate, not a second pane.
Which style presets and fonts can I use?
Normal starts with Arial-compatible Arimo. Formal uses Times-compatible Tinos, 12pt text, 1.5 spacing, justified paragraphs and one-inch margins. Kagantic uses Silkscreen headings, VT323 body text and DotGothic16 code, with navy frames and hard blue offsets on white. Override individual fonts, sizes, spacing, alignment and page settings without losing its treatment. Settings actions stay accessible while scrolling; Done returns to the document’s current caret or selection.
Does it remember my style and last file?
Yes: presets, bundled font choices, sizing, spacing, alignment and PDF settings are remembered in this browser. Imported font files stay tab-only and must be loaded again. Chrome/Edge can remember a native read-only file reference, not its contents. Returning reads that original file afresh if permission remains granted; otherwise choose File → Reopen (Alt/Option+E). A moved/deleted file cannot be restored from a cached copy. File → Forget (Alt/Option+V) removes the reference without deleting your original or clearing the active draft. Firefox/Safari and file-input fallback require selecting the file again because they do not expose a reusable path. Draft edits are never saved automatically.
Can I use actual Arial or Times New Roman?
Yes, through Styles → Font details & loading. Load installed fonts where browser permission-based access is available, or select four static TTF/OTF files from one family: regular, bold, italic and bold italic. These files stay in the tab and are embedded in the PDF. Microsoft fonts are not bundled; the included Arimo/Tinos alternatives are clearly labelled. You need the appropriate font licence and editable outline/subsetting permissions; see Microsoft’s font FAQ.
How are the Kagantic font styles handled?
The original pixel faces are included. Where VT323 or DotGothic16 has no designed bold/italic variant, documented OFL-derived faces provide emphasis; Silkscreen keeps its genuine bold face and derived italics. Ğ/ğ retain each selected family’s G/g shape with a matching cup accent. Dotless ı reuses Silkscreen’s exact undotted i outline and metrics; VT323 and DotGothic16 keep native dotlessi, without cropping, scaling or Roboto substitution. Same-family Turkish subsets cover Ğğı in all four styles with identical screen/PDF bytes and unchanged originals. Only quotation marks use the focused Roboto override. Other missing Silkscreen glyphs use VT323, then Roboto. Sources, derivations and licences are listed below. No logo or ownership footer is added.
Which shortcuts avoid three-key combinations?
Every formatting/file action uses one modifier and one key. Ctrl/Command: O opens, S downloads Markdown, P prints PDF, Z/Y undo/redo, B/I emphasis, K link, E inline code. Alt/Option: L bullets, O numbered list, T tasks, X strike, B code block, Q quote, G table, H page break, R Edit/Read, S styles, P PDF download, K help, N new, F File menu, W Tools menu, C spelling & grammar, E reopen, V forget last-file reference, D filename, J heading selector, U guide, 0 paragraph, 1–6 headings. In spelling review Alt/Option+C rechecks; Escape closes the dialog. Selecting text automatically shows nearby formatting controls; Tab moves into them. In Styles, Alt/Option+F adds font files; +A/+T load installed Arial/Times New Roman where supported. Typography fields retain native Tab/arrow navigation and dialog text input. Ctrl+L stays with the browser. Hold a modifier for control hints, hover for a tooltip, or open File → Keyboard shortcuts.
Does spelling and grammar checking send my writing to a service?
No. A same-origin worker loads only the selected local checkers: Turkish morphology and lexical resources, or pinned native Hunspell/WASM 0.3.0 dictionaries for the other languages. Tools offers English (US/UK), Turkish, German, French, Spanish, Italian, Portuguese (Brazil/Portugal), Dutch, Polish and Russian. Select one or two; English (US) + Turkish is the default. A word accepted by either checker is valid. Other non-English dictionaries provide spelling only. Local English rules cover word spacing, repeated words, articles, common verb agreement, participles and modal “have”; mixed-language sentences conservatively suppress language-specific rules when foreign-language evidence is present. This is not comprehensive contextual grammar checking; names, unselected languages and intentional wording may be flagged. Hover or tap an underline, use Alt/Option+Down at the caret, or open Tools → Spelling & grammar (Alt/Option+C). Suggestions change only that occurrence, with undo/redo retained; stale results cannot replace changed source. Words split across formatting boundaries require manual editing. Dismiss applies to the same issue and wording for the selected languages in this tab only. Tools can hide the counter or disable background checking; only toggle states and allowlisted language IDs are saved, never document text or dismissed words. Reading time rounds up at 200 words/minute (empty = 0 minutes). Engine/dictionary licences, checksums, original source and lexical attribution are linked from the dependency inventory; the reused English-US dictionary has its original notices.
How does Turkish checking handle suffixes and casual writing?
It uses Starlang’s Turkish finite-state morphological analyzer, spellchecker and deasciifier rather than an application-maintained list of word exceptions. Roots and productive suffix chains handle forms such as kitaplarımızdakilerden. A full upstream Turkish token-headword supplement from Wiktionary/Kaikki covers additional colloquial and vulgar vocabulary, including naber and bi; explicitly labelled misspellings are excluded. Upstream correction and word-boundary rules generate suggestions such as geliyormusun → geliyor musun, and a lazily loaded local n-gram corpus ranks candidates using nearby words. Nothing is rewritten without your approval. A valid word such as kanişler is not an error merely because you intended a different word. This is not semantic inference, exhaustive slang recognition or complete Turkish grammar checking. See the engine/source inventory and separate CC BY-SA lexical attribution.
How do I insert a page break?
Type a standalone --- and press Enter, use Page break in the toolbar or Alt/Option+H. Parsed *** and ___ rules also act as page breaks. Edit and Read show a divider; exported PDFs start the following content on a real new page without rasterizing text. Rules inside inline or fenced code stay literal. A leading rule does not start YAML front matter.
Will the PDF be an image or have a watermark?
No. The PDF is generated from the document’s text and formatting, not from a screenshot or a printed webpage. Text remains selectable and searchable. The export does not add a logo, watermark, page URL or browser header/footer.
Can I import a scanned PDF?
Text extraction needs an embedded text layer. For scanned or image-only PDFs, first run OCR in the PDF workspace, then open the searchable PDF here. Review extracted reading order; the original layout, tables and images are not recovered as editable document structures.
What happens to HTML and images in Markdown?
Raw HTML is treated as literal text, not executable page content. Image references are shown as text placeholders rather than fetched from remote hosts. Normal links open only when you choose them.
Does the editor work on a phone?
Yes. The text column fits the screen with smaller gutters and padding, without shrinking the text. Editing and reading keep the same writing edges. File actions and formatting remain accessible, and typography settings use a touch-friendly dialog. For large documents or PDFs, device memory and processing speed still matter.