@lingui/format-po/dist/po.d.cts

Gettext PO format for Lingui Catalogs

import { CatalogFormatter } from '@lingui/conf';

type PoFormatterOptions = {
    /**
     * Print places where message is used
     *
     * @default true
     */
    origins?: boolean;
    /**
     * Print line numbers in origins
     *
     * @default true
     */
    lineNumbers?: boolean;
    /**
     * Print `js-lingui-id: Xs4as` statement in extracted comments section
     *
     * @default false
     */
    printLinguiId?: boolean;
    /**
     * By default, the po-formatter treats the pair `msgid` + `msgctx` as the source
     * for generating an ID by hashing its value.
     *
     * For messages with explicit IDs, the formatter adds a special comment `js-lingui-explicit-id` as a flag.
     * When this flag is present, the formatter will use the `msgid` as-is without any additional processing.
     *
     * Set this option to true if you exclusively use explicit-ids in your project.
     *
     * https://lingui.dev/tutorials/explicit-vs-generated-ids#using-custom-id
     *
     * @default false
     */
    explicitIdAsDefault?: boolean;
    /**
     * Custom attributes to append to the PO file header
     *
     * @default {}
     */
    customHeaderAttributes?: {
        [key: string]: string;
    };
    /**
     * Print values for unnamed placeholders as comments for each message.
     *
     * This can give more context to translators for better translations.
     *
     * By default first 3 placeholders are shown.
     *
     * Example:
     *
     * ```js
     * t`Hello ${user.name} ${value}`
     * ```
     *
     * This will be extracted as
     *
     * ```po
     * #. placeholder {0}: user.name
     * msgid "Hello {0} {value}"
     * ```
     *
     * @default true
     */
    printPlaceholdersInComments?: boolean | {
        limit?: number;
    };
};
declare function formatter(options?: PoFormatterOptions): CatalogFormatter;

export { type PoFormatterOptions, formatter };