[GUI Plugin] Import List

[BetterRed]

Moderator Notice

@marm2017 - Please post in English - a Google translate of Spanish, French, whatever is normally adequate? See my my edit to post 300. The maintainer of the plugin may not understand Spanish.

Thanks

BR

[Terisa de morgan]

The problem is how you define the language. You have to use the ISO 639-2 code (Spa for Spanish, Eng for English) instead of the label. In that way it works fine. So, the only problem is that the plugin discard a field that it doesn't know how to translate.

---

El problema es cómo defines el idioma. Tienes que usar el código ISO 639-2 (Spa para español, Eng para inglés) en lugar de la etiqueta. Así va bien. Por tanto, el único problema es que el plugin descarta un campo que no sabe cómo traducir.

[davidfor]

Originally Posted by Terisa de morgan

The problem is how you define the language. You have to use the ISO 639-2 code (Spa for Spanish, Eng for English) instead of the label. In that way it works fine. So, the only problem is that the plugin discard a field that it doesn't know how to translate.

---

El problema es cómo defines el idioma. Tienes que usar el código ISO 639-2 (Spa para español, Eng para inglés) en lugar de la etiqueta. Así va bien. Por tanto, el único problema es que el plugin descarta un campo que no sabe cómo traducir.

My notes when I released the language supporting version included the names as well as the code. But, it's likely that the names are simple versions without any accented characters, effectively longer codes rather than the names. It could just be that I am mishandling the input and normalizing it or something might fix it.

@marm2017: Can you post or PM the CSV file so that I can test it. I can't promise to fix this, but, I'll have a look.

[Terisa de morgan]

Originally Posted by davidfor

My notes when I released the language supporting version included the names as well as the code. But, it's likely that the names are simple versions without any accented characters, effectively longer codes rather than the names. It could just be that I am mishandling the input and normalizing it or something might fix it.

If I use as name "English" instead of "Inglés" it works but "Chino" (without accented characters) doesn't work. So, I'm afraid the problem is the language

[marm2017]

Originally Posted by Terisa de morgan

If I use as name "English" instead of "Inglés" it works but "Chino" (without accented characters) doesn't work. So, I'm afraid the problem is the language

Thanks for answering. I will keep trying.

[davidfor]

I've looked at the way the languages are being imported and realised that I had missed a case. This meant that it was not correctly handling language names in the local language. It was handling the two or three letter codes plus the English name for the language. This change will allow the language to be entered in the language used for the calibre interface.

For example, if using Spanish, any of the following can be used to set the book language to Spanish:

- Español
- esp
- es
- es-SP (and any other code like this)
- Spanish

I have tested this with the CSV file that marm2017 sent, with a few changes. Please test and tell me if it works properly.

[marm2017]

Originally Posted by davidfor

I've looked at the way the languages are being imported and realised that I had missed a case. This meant that it was not correctly handling language names in the local language. It was handling the two or three letter codes plus the English name for the language. This change will allow the language to be entered in the language used for the calibre interface.

For example, if using Spanish, any of the following can be used to set the book language to Spanish:

- Español
- esp
- es
- es-SP (and any other code like this)
- Spanish

I have tested this with the CSV file that marm2017 sent, with a few changes. Please test and tell me if it works properly.

Problem solved. Now it works perfectly.
Thank you very much.
Happy 2018

[Terisa de morgan]

I have a question about this plugin. I want to import some data to columns of type "Text, fixed set of values" (excuse the wording, I use the Spanish interface, it's like an enumerated column), but they don't appear in the list of fields I want to import. Is that right?

[davidfor]

Originally Posted by Terisa de morgan

I have a question about this plugin. I want to import some data to columns of type "Text, fixed set of values" (excuse the wording, I use the Spanish interface, it's like an enumerated column), but they don't appear in the list of fields I want to import. Is that right?

I had to look at the code. Not, it doesn't display these types of columns. I'm not sure why. It's probably because there is no way to ensure the input is in the set of values. I think the only thing you could do would be to reject the value and not set it if it isn't valid. Which is effectively what happens with the language.

I'll try and have a look over the weekend. If doing the above isn't hard, I'll add it.

[Terisa de morgan]

Originally Posted by davidfor

I had to look at the code. Not, it doesn't display these types of columns. I'm not sure why. It's probably because there is no way to ensure the input is in the set of values. I think the only thing you could do would be to reject the value and not set it if it isn't valid. Which is effectively what happens with the language.

I'll try and have a look over the weekend. If doing the above isn't hard, I'll add it.

Thank you very much!

[davidfor]

It turned out the change to handle enumeration columns or "Text, but with a fixed set of permitted values" was simple. So here is a beta that does this.

This will add the "Text, but with a fixed set of permitted values" columns to the list of fields that can be selected when importing. But, it makes no attempt to validate the values. If the value in the import file is in the list of permitted values, it will be used. If it isn't, then it will be ignored. No error will be shown. This is similar to the languages column.

I have done a little testing with my one-and-only column of this type. It seems to work. Tell me if there are any problems. If I hear everything is OK, I'll release this properly next week.

[Terisa de morgan]

Thank you!, it works totally fine for me (two columns from my side, with right values, I haven't tested wrong values).

[davidfor]

Version 1.3.0 of the plugin was released earlier. The changes in this release are:

• Change: All importing columns of type "Text, but with a fixed set of permitted values".
• Fix: Improve handling of languages.
• Change: Use calibre author decoding instead of custom code. This uses the tweak.

These changes were included in the last few betas.

As usual, calibre will announce the update as available. And if there are any problems, please report them here.

[Inukami]

Hi,

I'm getting the following error when I try and import a CSV book list using the Import List plugin.

ERROR: Unhandled exception

Error: new-line character seen in unquoted field - do you need to open the file in universal-newline mode?

I'm not sure what I'm doing wrong. What does that error message mean? The CSV list has columns that match my library. I would greatly appreciate any help you can provide or step by step instructions.

Thanks,

Inukami

[theducks]

Originally Posted by Inukami

Hi,

I'm getting the following error when I try and import a CSV book list using the Import List plugin.



I'm not sure what I'm doing wrong. What does that error message mean? The CSV list has columns that match my library. I would greatly appreciate any help you can provide or step by step instructions.

Thanks,

Inukami

That says there ia ONE or more DATA (records) locations with the wrong data type in a Numbers only position. (A real PITA to spot in a large table)

"words", Numbers, Numbers, "words",Numbers, Numbers,

One of your numbers might have a comma, throwing
off the type trying to be inserted into the numbers after the second 'word' (in this example)

Try importing the CSV into a NEW spreadsheet, then verify the suggested column types (a text instead of Numeric or date)