Bugs and feedback

1. When typing into the search box at the bottom of the Terms list, it often loses focus and kicks the cursor out of the box. I'll type a couple letters at a time and it stops accepting input until I click it again.
   i.imgur.com/Nvhbs3T.png


2. When using the search, the selection shortcuts at the bottom (All, None, Used, Not Used, Missing) select from the full Terms list, not from the ones that are visible.


3. The search box in the Terms list resets every time you select a different object.


4. Typing in a Category name doesn't let you type a '/' at the end. This prevents me from entering 'GUI/MenuTitle' unless I type the 'M' then go back and insert the '/'.


5. If an inferred Term (possibly any Term) has a newline in it, it doesn't display properly in the popup list on Localize scripts. Perhaps it should replace \r and \n characters with explicit "\r" and "\n" strings (for display purposes only).
   i.imgur.com/BzxO78r.png


6. Sub-Categories don't show up as new sheets in Google Drive. They show up on sheet for the root Category (e.g. "GUI/Button/Back" will show up as "Button/Back" on the "GUI" sheet).


7. I don't see a way to choose the language you want to display in the Editor. I'd like to be able to select the current language in the Editor and have all the Localize scripts change to the selected language without need to play the game.


8. The Assets tab on the Language Source throws GUISkin related warnings.
   i.imgur.com/KnwgDec.png

Frank wrote:

Sub-Categories don't show up as new sheets in Google Drive. They show up on sheet for the root Category (e.g. "GUI/Button/Back" will show up as "Button/Back" on the "GUI" sheet).

That's actually the intented behavior. Google doesn't support hierarchical tabs, thats why only the root category its converted to a sheet. Given that you could have tons of subcategories, and most of them will contain just a few terms, It could generate lot of very small sheets.

In case of needing to make sheets for the subcategories as well, you could do "GUI_Dialog" instead of "GUI\Dialog".

Nonetheless, do you think that it will be more intuitive/better to generate a sheet for each category node?

1. If a term was auto-translated and hasn't been 'approved', when exporting it to Google Drive the Categories are included in the translated text. So Term "InputOptions" in Category "Menu Title" will be saved to Google Drive as "Menu Title / InputOptions" even though it's configured as "Input" locally in the Language Source prefab. Then, the next time I sync with Google Drive, the correctly configured local Term gets overwritten by the incorrect Google Drive Term.
   
   To add context, I've been completely ignoring that Approve button. I have no idea what it is supposed to do. If I approve the translation, the text is kept. If I don't approve the translation, the text is still kept, so what's the purpose of having to approve it? If I don't like the translation, shouldn't I just be able to Undo? Ctrl+F through the documentation doesn't mention anything about approving translations. Also, this is another button with no icon on it.


2. There are several cases where the Language Source prefab is not marked dirty. This means Unity doesn't know to save it and data is lost when you close the Editor. I haven't dug in, but it looks like changing the Description on a Term doesn't mark the prefab, nor does syncing against Google Drive even when that causes Terms to change.
   
   There are likely other cases and they will probably be pretty hard to suss out. However, since this causes the user to lose their work, it's a pretty important thing to test thoroughly and address. I notice it locally because I made changes in the Language Source inspector, saved assets in Unity, and went to commit my changes through SVN. The prefab didn't show up as modified. I then forced it to change by adding a new dummy term and saving assets. The next time I tried to commit the prefab contained all my previous changes in addition to the dummy Term.
   
   Worse comes to worst, I'd rather brute force it and always mark the prefab as dirty as soon as it gets inspected than risk losing work.


3. When exporting to Google Docs, the Term column width and the word wrapping on translated text columns are reset. I'd prefer to be able to set these myself and have the changes stick. The Terms column is too narrow and clips my Terms and some of the translations are long, so I'd rather them wrap than run off the screen or get clipped.