-
Notifications
You must be signed in to change notification settings - Fork 0
Transifex and Crowdin can display all strings and translation history, comments, etc. in 1 page via Ajax. In particular, Crowdin can display the list of strings, history, comments, and candidates within a single page. On the other hand, Weblate requires one window to be open to view the comments associated with a single string. So, Huge number of windows open to To view history and others' comments in Weblate.
Weblate can display all translation rates at 1 page. Excellent. Not so with Transifex and Crowdin, which requires many steps to detect additional translation strings.
In general, it would be convenient if your language is displayed first. I'm Japanese.
Editor: All information can be aggregated on 1 page, List, Filter, Sort, Input field. However, The following must be clicked to switch : History, Suggestions, Comments, Context. The presence or absence is clearly indicated by a numeric badge. Context includes: variable name, file name.
Editor: All information is aggregated. List, Filter, Sort, History, machine translation, Comments, Context, Used in other languages. Context includes: variable name only. If there are many participants, we can vote plus or minus. Crowdsourced voting systems are excellent. However, Since the list is a page system, If there are a large number of items, it will take time to return to the previous item. 50 items per page. Perhaps more strings per page would be good.
Changes are easily recognizable, highlighted in red and green in Weblate.
Editor: Single mode : Translation mode for one string at a time. Context includes: variable name, file name,
One item at a time, no other platform or editor has this. Very inefficient. It is unlikely that a skilled translation contributor would use it. This mode is difficult to use if you want to unify terminology. You can't easily go back 10 units. There are many margins and information is not aggregated. There is 2-3 times more space than Crowdin to display one history.
Editor: List mode (Zen mode) : There is only variable names. Skilled translation contributors will primarily use this mode. Because even when editing a file with a text editor, it is in list mode. However, If you want additional information, you will need to open more windows. Looking at comments and history is an enormous amount of work. So, more users will miss the comments.
Project search targets include descriptions.
Project list: To see the progress (translation percentage), you need to open each part of the project. There is no list of projects in which I participate. It takes a huge number of clicks just to find a project to join. It's crazy.
The list I joined is on the mini-menu.
Top page of non-participating projects.
Project list next page: Because they are listed in percentage order, it is difficult to find them if they are low. The Joined Project Top is similar to this, But there are untranslated numbers.
Project search targets include descriptions.
Project list: Crowdin will notify you of the addition of new strings. But I only know the update time in the list. This update time doesn't mean adding a new string.
Project list next page: Your language will be displayed at first.
Project search targets is only project name.
Progress is very clear. You can recognize more before you click. One click from this list opens the untranslated string.
Wordpress.org is for blog software and its plugins, so it differs slightly from the above. However, there are characteristics that I would like to explain.
Editor: Translation memory shows changes in red and green. This displays differences from similar source texts. Include changes from the previous original text.
The list, history, translation memory, Comment, and Context (References) are aggregated on 1 page. Context is excellent, and the actual code can be showed by clicking on the file name. However, There are only 15 items per page and it takes time to navigate. I open about 20 pages at a time to address the listing issue. There is no string search function. An external editor is required for searching. Must work with an external editor.
Project search targets include descriptions. You will not know if it is eligible for translation until you open the page several times.
https://translate.wordpress.org/locale/ja/default/stats/plugins/ :