hlp-ai / mt-core Goto Github PK

Writing doc for a complete example.

At present, translation service is accessed through http. This may be unsafe and inappropriate for mobile APP.

Now, access checking can be done for doc translation, and length limit can be set for text translation.

Are the length limit based on chars or pages?

Product-ready UI.

In backend of translation service, API key or Token is supported. It controls who can access translation interface and the limit for translation.

However, in Web browser, users cannot input API key or Token now.

API key or Token can be set in the same UI for translation endpoint just like mobile APP.

In GUI, the applied fiters can be choosed and the parameters of fiters can be configured.

In mobile browser, after clicking "Switch to PC version", the page is still redirected to mobile page.

This is because the onload event handler in text.html check UA without any condition.

When users browse Web UI with mobile phones, sytem should be redirected to UI adapted to mobile browsers.

The UI for mobile browsers should be simpler than that for PC browsers.

Current file translaton UI use build-in input button with type file to upload file to translate. It is not beautiful.

File uploading in Baidu document translation UI (https://fanyi.baidu.com/mtpe/#/editor/quickImport) can be a reference.

Display translation progress during translation, which is more friendly to users.

Add Corpus->ExtractZips menu, which corresponds to extract_zips.py.

After translation, table, formula, text style and so on should be preserved.

Display request error in Web.