Incorporate i18n into UI elements (#1471)

* Update zh-tw string table (till 975343d2)
* Prepare localization table
* Implement i18n for Performers & Tags
* Add "add" action strings
* Use Lodash merge for deep merging language JSONs

The original implementation does not properly merge language files, causing unexpected localization string fallback behavior.

* Localize pagination strings
* Use Field name value as null id fallback

...otherwise FormattedMessage is gonna throw when the ID is null

* Use localized "Path" string for all instances
* Localize the "Interface" tab under settings
* Localize scene & performer cards
* Rename locale folder for better compatibility with i18n-ally
* Localize majority of the categories and features
This commit is contained in:
Still Hsu
2021-06-14 14:48:59 +09:00
committed by GitHub
parent 46bbede9a0
commit 3ae187e6f0
105 changed files with 3441 additions and 1084 deletions

View File

@@ -1,18 +1,25 @@
import React from "react";
import { Form } from "react-bootstrap";
import { FormattedMessage } from "react-intl";
import { Link } from "react-router-dom";
export const SettingsToolsPanel: React.FC = () => {
return (
<>
<h4>Scene Tools</h4>
<h4>
<FormattedMessage id="config.tools.scene_tools" />
</h4>
<Form.Group>
<Link to="/sceneFilenameParser">Scene Filename Parser</Link>
<Link to="/sceneFilenameParser">
<FormattedMessage id="config.tools.scene_filename_parser.title" />
</Link>
</Form.Group>
<Form.Group>
<Link to="/sceneDuplicateChecker">Scene Duplicate Checker</Link>
<Link to="/sceneDuplicateChecker">
<FormattedMessage id="config.tools.scene_duplicate_checker" />
</Link>
</Form.Group>
</>
);