Error to Export to Google

More
4 years 9 months ago - 4 years 9 months ago #197 by sandolkakos
I can't export my LanguageSource terms to Google Drive.

I've described the error in that image:
Last edit: 4 years 9 months ago by sandolkakos.

Please Log in or Create an account to join the conversation.

More
4 years 9 months ago #198 by Frank
Replied by Frank on topic Error to Export to Google
Hi,
Can you try exporting to a CSV file instead and opening the file in any Text Editor. It could be that you have some invalid character in your terms/translations that are skiping the rest of the characters in the string I send to the google doc.

If it exports correctly then check for any weird character and let me know which one it is so that I could add support for those.

Thanks,
Frank

Are you :-) Give I2L 5 stars!
Are you :-( Please lets us know how to improve it!
To get the betas as soon as they are ready, check this out
The following user(s) said Thank You: sandolkakos

Please Log in or Create an account to join the conversation.

More
4 years 9 months ago - 4 years 9 months ago #199 by sandolkakos

Attachment Localization_Exported.zip not found


Thanks for the attention, Frank.
The exported CSV is in the attachment files.
Attachments:
Last edit: 4 years 9 months ago by sandolkakos.

Please Log in or Create an account to join the conversation.

More
4 years 9 months ago - 4 years 9 months ago #200 by Frank
Replied by Frank on topic Error to Export to Google
Hi,
I opened the csv file you attached and was able to reproduce your issue.

The terms are actually been exported fine to google docs, but they are two categories in your terms.

The plugins generates one spreadsheet tab for each of the categories.
If you check your spreadsheet, you will see that the first tab has only 1 term, but next to that tab there is another one named "Default" and all the other terms are in that category.

You can fix that issue by modifying the categorized term.

Your term is:
[ff0000]You need to Login and Accept the APP in your Facebook Account.\n\nPlease click in the[-] [0000ff]Login button[-] [ff0000]bellow.[-]",Text,,"[ff0000]You need to Login and Accept the APP in your Facebook Account.

The plugin sees the '\' in the string and uses the first part of the string as the category (category1\category2\term")

I2 Localization is able to encode the carry returns, so you don't need add the \n\n.
One easy fix is to open the csv in a notepad and change that string by:
"[ff0000]You need to Login and Accept the APP in your Facebook Account.

Please click in the[-] [0000ff]Login button[-] [ff0000]bellow.[-]",Text,,"[ff0000]You need to Login and Accept the APP in your Facebook Account."

Attached you can find the fixed CSV file, you could import that file into the language source and it should work correctly.

Please, let me know if you find any issue or have any other question,
Frank


Attachment Localization_Exported1.zip not found


Are you :-) Give I2L 5 stars!
Are you :-( Please lets us know how to improve it!
To get the betas as soon as they are ready, check this out
Attachments:
Last edit: 4 years 9 months ago by Frank.
The following user(s) said Thank You: sandolkakos

Please Log in or Create an account to join the conversation.

More
4 years 8 months ago - 4 years 8 months ago #214 by sandolkakos
Thank you very much, Frank.

That Term was an old added in my first test, when I was migrating from the Old NGUI Localization :)

One more question:
Are there any problem if I want to continue using "\n" only in the Translation texts? I understood if I use the "\n" in the KEY of the Term it will generate the errors with categories, but what about using "\n" inner translation texts?
Last edit: 4 years 8 months ago by sandolkakos.

Please Log in or Create an account to join the conversation.

More
4 years 8 months ago #215 by Frank
Replied by Frank on topic Error to Export to Google
You can add \n to the translated texts if you need it.
Nonetheless, I2 Localization will convert the carry returns into "\n" automatically so that NGUI and other plugins could show texts with multiple lines.

That way:
"Text
text2"

becomes internally "Text\ntext2"

however, if you type "Text\ntext2" in the translation, then it will be used as "Text\\ntext2"

Are you :-) Give I2L 5 stars!
Are you :-( Please lets us know how to improve it!
To get the betas as soon as they are ready, check this out
The following user(s) said Thank You: sandolkakos

Please Log in or Create an account to join the conversation.

Time to create page: 0.129 seconds
Template by JoomlaShine