Details
-
Bug
-
Resolution: Fixed
-
None
-
Low
-
Fix typos and textual inconsistencies in configuration labels and descriptions.
-
Empty show more show less
Description
Typos
auto-propgate
invokation
punctiation
e.g [full stop missing]
If one line of a segment is to long, a new line is automatically added
superseeded
For moreinfo see the branding
Pattern for a XML reference file
Okapi bconf is not used for CSV iimport
CSV import: ecnclosure
this is determined by another configuraiton parameter
If checked, informations are added
and if this checkbox is checcked
If checcked, whitespace is preserved,
ressources
azureaccount
accessable
date is shown.If set to
immidiately
keeped
prefered
from the users browser
Errors will be send to translate5s
occurence
Okapi server used for the a task
If emtpy, nothing is loaded
The imported task is send as raw JSON in that request
successfull
Inconsistencies - the preferred values are in bold!{}
api vs API vs Api
url vs URL
MicroSoft vs microsoft vs Microsoft
pretranslated vs pre-translation vs pretranslation
matchrate vs match rate vs match-rate
languagetool vs LanguageTool vs LanguagaTool vs languageTool
languagecloud vs LanguageCloud
TermTagger vs termtagger
Websocket vs WebSocket
Extjs vs ExtJS
TermPortal vs termportal
US English vs UK English
Currently, US English (like “optimized”) and UK English (like “behaviour”) are both used. Maybe that’s intentional, I would appreciate it if it was consistent.
→ Export the whole table as SQL and choose the correct spellchecker on the exported data. Modify the SQL so that its updates instead of INSERT or do it on CSV base.
User addressed as “he”
In strings like “When an assigned user leaves a task, he is asked, if he wants to finish or just leave the task.” the user is addressed as “he”.
Should be solved by repeating "the user".