Resources, Fonts, and Prompts

When the server lacks the font you need, or the translator needs a custom prompt, upload your own font and prompt files in the “Options” tab of the web workspace and select them from the configuration dropdowns. This guide focuses on ordinary-user resource upload, listing, deletion, and configuration use; admin-managed shared fonts and prompts are described in Administrator interface, and HTTP endpoint contracts live in Config, environment, and resources API.

UI and API scope

• This guide covers web user resources: upload, list, and delete fonts (TTF/OTF/TTC) and prompts (JSON), plus the render.font_family and translator.high_quality_prompt_path configuration fields.
• Upload-section visibility is decided by can_upload_fonts and can_upload_prompts returned from /user/settings; whether deletion is allowed is decided by the server-side permission check.
• It does not cover admin-managed shared fonts and prompts (/upload/font, /upload/prompt, /fonts, /prompts management endpoints), nor the desktop prompt-list CRUD (see Prompt list, apply, and preview).
• This page never shows real API keys, private prompt bodies, or user file contents.

Use it in the Web UI

Find the resource and configuration entries

After signing in, the right settings panel of the main workspace has four tabs: “Basic Settings”, “Advanced Settings”, “Options”, and “API Keys (.env)”.

• “Font Management” and “Prompt Management” are located in the right column of the “Options” tab.
• The corresponding upload section is shown only when can_upload_fonts / can_upload_prompts is true; hiding the section does not mean the server forbids it, and the permission is ultimately enforced by the server.
• The render.font_family dropdown is on the “Advanced Settings” tab (render group), and the translator.high_quality_prompt_path dropdown is on the “Basic Settings” tab (translator group). Both render as dropdowns even when the option list is empty, with a “-- 不使用 --” empty option.

Upload fonts

1. On the “Options” tab, click “上传字体文件” (Upload font file) in the “Font Management” area.
2. The file picker only accepts .ttf, .otf, and .ttc; the backend accepts exactly the same three formats.
3. After a successful upload the frontend re-requests /config/options, refreshes the Font dropdown and the uploaded-font list, and logs “字体上传成功” (Font uploaded successfully).

Upload prompts

1. On the “Options” tab, click “上传提示词文件” (Upload prompt file) in the “Prompt Management” area.
2. The file picker only accepts .json; the server-side resource_service PROMPT_FORMATS is .txt/.json, but the prompt loader (load_prompt_file) parses only .json/.yaml/.yml, so use JSON.
3. After a successful upload the Custom Prompt dropdown and the uploaded-prompt list are refreshed.

Delete resources

• Font rows always show a “删除” (Delete) button; prompt rows show “删除” only for user resources whose path contains user_resources, while server-provided prompts show a “服务器提示词” (Server prompt) label.
• Clicking “删除” opens a confirmation dialog; after confirmation the delete endpoint is called and the frontend refreshes dropdowns and lists.
• The frontend does not hide delete buttons according to can_delete_fonts / can_delete_prompts; the server rejects requests without permission with 403.

Parameters and options

For detailed parameter information (UI names, storage keys, default values, and effective stages) on this page, see the reference index: UI Options Reference.

Font

The “Font” dropdown is on the “Advanced Settings” tab (render group) and selects the font used for typesetting rendering and editable PSD text layers; options are the deduplicated union of the server-shared font directory and the current user's uploaded fonts. See Typesetting and Rendering for details.

Custom Prompt

The “Custom Prompt” dropdown is on the “Basic Settings” tab (translator group) and selects the custom prompt file used for translation requests; options come from the server prompt directory (system prompts excluded) plus the current user's uploaded prompts. See Context and Prompts for details.

Requests and data flow

Resource lifecycle

flowchart TD
    A["Options tab: Font Management / Prompt Management"] --> B{"can_upload_fonts / can_upload_prompts?"}
    B -->|no| Z["Upload section hidden"]
    B -->|yes| U["Pick .ttf/.otf/.ttc or .json file"]
    U --> C["POST /api/resources/fonts or /prompts"]
    C --> V{"Permission and format check"}
    V -->|403| E1["No upload permission"]
    V -->|400| E2["Unsupported format"]
    V -->|200| S["Save file + index record + refresh dropdowns and lists"]
    S --> D["Delete button in the list"]
    D --> X["DELETE /api/resources/fonts/{id} or /prompts/by-name/{filename}"]
    X --> R{"File exists and belongs to current user?"}
    R -->|no| F["400 or 404 rejection"]
    R -->|yes| OK["Delete file and index record"]

Limitation: both upload and delete require a session and each checks resource permissions; even when the UI shows a button, a request without permission is rejected by the server with 403.

How the font dropdown merges

flowchart LR
    SF["Shared fonts/ directory (admin-managed)"] --> FL["load_font_file extracts family"]
    UF["user_resources/fonts/ current user uploads"] --> FL
    FL --> M["Deduplicated sorted font_family list"]
    M --> D["Font dropdown render.font_family"]
    D --> R["Typesetting render and PSD text layers"]

Note: /config/options returns family names only, not file paths; load_font_file registers the font into the Qt font library and returns the family, so newly uploaded fonts appear in the dropdown only after options are re-requested.

How the prompt dropdown merges

flowchart LR
    DD["dict/ server prompt files"] --> DP["dict/{filename} path"]
    UP["user_resources/prompts/ current user uploads"] --> UPP["Relative resource path"]
    DP --> M["Custom Prompt dropdown high_quality_prompt_path"]
    UPP --> M
    M --> N["normalize_server_resource_path + BASE_PATH"]
    N --> L["load_custom_prompt parses"]
    L --> S["OpenAI/Gemini system prompt"]

Note: the dict/ scan excludes the four system stems system_prompt_hq, system_prompt_hq_format, system_prompt_line_break, and glossary_extraction_prompt; user prompt paths come from get_user_prompts and are appended after server prompts, so server prompts appear first and user prompts follow.

Permissions, security, and limits

• After uploading a font, reload the configuration options first (focus the dropdown or sign in again) before it appears in the selector; if the font is not registered, the renderer falls back to the default family.
• Prompts must be parseable JSON; .txt can be uploaded but cannot be loaded and is treated as missing during translation.
• Admin-managed shared fonts/prompts and user private resources are two separate storages and permission sets: shared resources are covered in Administrator interface, and the HTTP contracts for both are in Config, environment, and resources API.
• Resource permissions come from the user-group configuration (can_upload_fonts, can_upload_prompts, can_delete_fonts, can_delete_prompts); hiding UI elements only affects display and cannot bypass server checks.
• Uploaded filenames are sanitized and duplicates get numeric suffixes; do not rely on the original uploaded filename.

See the reference index: UI Options Reference.