bazarr/frontend
Vitiko 547f8c428d
Added feature to treat couples of languages as equal when searching for subtitles
* Add 'Language-equals' support

This feature will treat couples of languages as equal for list-subtitles
operations. It's optional; its methods won't do anything if an empy list
is set. See more info at docstrings from 'subliminal_patch.core'.

For example, let's say I only want to have "Spanish (es.srt)" subtitles
and I don't care about the differences between Spain and LATAM spanish.
This feature will allow me to always get European Spanish even from
LATAM Spanish providers like Argenteam and Subdivx.

Example for config.ini:

language_equals = ['spa-MX:spa']

(Which means all Latam Spanish subtitles from every provider will be
converted to European Spanish)

* Add PT and ZH language tests

* Add HI and Forced parsing for language pairs

Format example: ["en@HI:en", "es-MX@forced:es-MX"]

* Update languages.py

* Update API definition to reflect the previous change

* Add language equals table to the UI (test only)

* Add global language selector and get language from code3 utilities

* Add unit tests for language equal feature

* Add encode function to language equal feature

* Add CRUD methods to the language equals panel

* Add equals description

* Add parsing support for alpha3 custom languages

* no log: add more tests

* Add forced and hi support to the language equal target

---------

Co-authored-by: morpheus65535 <louis_vezina@hotmail.com>
Co-authored-by: LASER-Yi <liangyi0007@gmail.com>
2023-05-27 09:38:55 -04:00
..
.husky no log: Add pattern parameter to the pretty-quick hook to limit the effective scope 2022-08-29 21:33:22 +08:00
config no log: Improve dev tools 2022-09-21 05:40:02 +08:00
public/images no log: fix favicon 2022-09-28 06:27:52 -04:00
src Added feature to treat couples of languages as equal when searching for subtitles 2023-05-27 09:38:55 -04:00
.env.development no log: Auto detect backend port and base_url during development 2022-03-17 12:01:22 +08:00
.eslintrc.json no log: Add warning when not writing camelCase in frontend project. We should fix those later 2023-02-20 14:36:43 +08:00
.gitignore Replace Bootstrap with Mantine (#1795) 2022-05-31 23:49:04 +08:00
.prettierignore Add Unit Tests to UI (#2015) 2023-02-10 23:10:13 +08:00
.prettierrc Refactored Web UI using React 2021-03-25 10:22:43 -04:00
README.md no log: Auto detect backend port and base_url during development 2022-03-17 12:01:22 +08:00
index.html no log: fix favicon 2022-09-28 06:27:52 -04:00
package-lock.json no log: Bump socket.io-parser from 4.2.2 to 4.2.3 in /frontend (#2150) 2023-05-26 10:45:10 +08:00
package.json no log: Bump @vitest/coverage-c8 from 0.25.8 to 0.28.5 in /frontend (#2130) 2023-05-25 23:23:15 +08:00
tsconfig.json no log: Setup unit tests for UI 2022-03-29 01:10:24 +08:00
vite.config.ts no log: Move setup file to src folder 2023-02-11 01:36:46 +08:00

README.md

Bazarr Frontend

Dependencies

  • Node.js
  • npm (included in Node.js)

Getting Started

  1. Clone or download this repository

    $ git clone https://github.com/morpheus65535/bazarr.git
    $ cd bazarr/frontend
    
  2. Install build dependencies in the project directory

    $ npm install
    
  3. (Optional) Duplicate .env.development file and rename to .env.development.local

    $ cp .env.development .env.development.local
    
  4. (Optional) Update your backend server's API key in .env.development.local

    # API key of your backend
    VITE_API_KEY="YOUR_SERVER_API_KEY"
    
  5. (Optional) Change the address of your backend server

    # Address of your backend
    VITE_PROXY_URL=http://localhost:6767
    
  6. Run Bazarr backend

    $ python3 ../bazarr.py
    
  7. Run the web development tool

    $ npm start
    

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode. Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits. You will also see any lint errors in the console.

npm run build

Builds the app in production mode and save to the build folder.

npm run format

Format code for all files in frontend folder

This command will be automatic triggered before any commits to git. Run manually if you modify .prettierignore or .prettierrc