Problems with CSV import

Hi,

The CSV file wasn't attached, can you please reattach it or email it to This email address is being protected from spambots. You need JavaScript enabled to view it.

If the terms are categorized (if they have the '/' or '\' character like in "Category/Term") then they will be imported, but in the terms tab at the top right there is a dropdown to allow you filter which categories you want to see.
By default it is set to "Everything", but if you clicked there it could remember any change you did and hide some of the categories.

I see that if you have a precreated CSV file most likely it will not have the correct format (missing Type and Description columns) so I will add in the next release (2.3.2) a fix for detecting if the Type and Descriptions are present and if not, just assume they are empty and load the rest as usual.

Thanks,
Frank

Hi,
I tested the CSV file you sent me and found that it has an extra column after the Desc.
Note the ",," after Desc.
Try opening that CSV in excel and removing that column.
Even with that column it does load all the languages but the first one is empty.

One thing I noticed is that the language section doesn't expand to cover the full screen height like the Terms list, so it gets a bit annoying having to scroll down to see all the languages. I will make that list expand to fill the empty space in the next release.


About the second issue (the list of term showing cut off), thats indeed a bug. As part of the optimizations for speed browsing long list of terms, I'm hidding the terms that are offscreen. But as the term list is now expanding to cover the full height of the screen if possible, then it goes longer than the predefined size (300 pixels).

I'm adding a fix for that in the next release as well, but you can change it right now by replacing "Height" by "Screen.height" in line 79 of the file I2\Localization\Editor\Localization\LocalizationEditor_Terms.cs

from:
into
Thanks for reporting that issue,
Frank