import issues with ixml files

15 views
Skip to first unread message

Maria Sosnowski

unread,
Nov 28, 2021, 7:40:53 PM11/28/21
to SKYIndexUsers

Happy Thanksgiving weekend to you all.

 

I’m using Sky 7, and I’m importing ixml files.  These were exported from a cindex user.  They use a “curly f” for figures (florin character).  When I import the file, I end up with only the entries that are not figures.  All of the entries with the curly f in the locator field are missing. 

 

Does anyone know why this is happening?  We have been doing a workaround, but it would be nice to make this work if there is something simple I’m missing. 

 

Thanks!

 

Maria

 

Deborah Patton

unread,
Nov 28, 2021, 7:50:02 PM11/28/21
to Maria Sosnowski, SKYIndexUsers
Would it annoy the cindex user to find the florin character and change it to something else (like a plain letter f) since it's clearly causing the problem? It might just be a font thing or maybe you need to define that character in the translation table ahead of time? Since you know it should be a florin, you can change it to that when you get the rest of the file imported.
I just had an instance in v8 where a Unicode character (that I pasted into SKY) showed as a square box but when I switched fonts to -- well what worked for me was to switch to Tahoma -- then it displayed properly. Some fonts work better with Unicode than others so maybe it's a font issue.  I use Georgia all the time because it's one that works well with Unicode usually, but not with this particular character.
Deborah

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
--
You received this message because you are subscribed to the Google Groups "SKYIndexUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skyindexuser...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/skyindexusers/075301d7e4b9%24c37e3570%244a7aa050%24%40index-plus.com.

Maria Sosnowski

unread,
Nov 28, 2021, 8:18:22 PM11/28/21
to Deborah Patton, SKYIndexUsers

They have been grouping all the figure entries, changing it to a plain f, and then sending that to me for import.  Then I send it back and they have to change it back.  This is going to be an ongoing project so I was hoping for a permanent fix.

 

You’ve given me some ideas though.  If I play with the translation table I can get it to import all the records, but I’m getting [u402] instead of the florin, and also code instead of apostrophes, etc.  So I can’t figure out how to use the translation table to get the florin fixed and also the other things that are now messed up.  If I don’t use the translation table, I don’t have issues with the apostrophes but the florin records don’t show up.

 

Thanks for your thoughts, it’s helpful.

 

Maria

Deborah Patton

unread,
Nov 28, 2021, 8:25:23 PM11/28/21
to Maria Sosnowski, SKYIndexUsers
I wonder if v8 would have fewer of the issues you're encountering since one of the goals of it was to have Unicode work better. I'd be happy to test that if you'd send me the .ixml file. I'd just test it, report to you about it and delete it. I'm on the east coast and am about to turn my machine off, but I'd do it first thing in the morning. Or you can get another SKY user with v8 test it.
It's worth finding out --
Deborah

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
To view this discussion on the web visit https://groups.google.com/d/msgid/skyindexusers/076001d7e4be%24ffe18d50%24ffa4a7f0%24%40index-plus.com.

Maria Sosnowski

unread,
Nov 28, 2021, 8:30:13 PM11/28/21
to Deborah Patton, SKYIndexUsers

Great idea – playing with this after reading your email made me wonder the same thing.  I just tried importing the 3 files I currently have into Sky 8 and they imported perfectly.  No translation, no changing any settings, just a perfect import. 

 

So I think I’ll be using Sky 8 for this particular client. 

 

Thanks for your ideas – they got me moving in the right direction!

 

Maria

Jochen Fassbender

unread,
Nov 29, 2021, 1:24:13 AM11/29/21
to skyind...@googlegroups.com
Wasn't it once mentioned that SKY 8 no longer supports the ixml format? Or do I mix things up?

Jochen


Deborah Patton

unread,
Nov 29, 2021, 5:07:49 AM11/29/21
to Maria Sosnowski, SKYIndexUsers
Yahoo! I've been using SKY 8 for several years (or so it feels) and I like it a LOT. Check out Locators and note what you can do. At this point two notes across two pages isn't a pain in the #$@!. Now I only have to type in 271-2n41-42 which displays as 271–72nn41–42 -- and I can format the setting so the n or nn is in italics or whatever. So many cool things with v8. It's like typing in xref instead of see or see also and it does it right every time. (There is an override for exceptions.)

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
To view this discussion on the web visit https://groups.google.com/d/msgid/skyindexusers/077001d7e4c0%24a795dff0%24f6c19fd0%24%40index-plus.com.

Maria Sosnowski

unread,
Nov 29, 2021, 9:32:57 AM11/29/21
to SKYIndexUsers

Thanks for your help.  I had a few things that behaved strangely when I used 8 so I went back to 7.  I have used it for books with tons of diacritics since being able to copy/paste those was so wonderful. 

 

I haven’t tried it for a couple of years, so this client will make me give it another go. 

Maria Sosnowski

unread,
Nov 29, 2021, 9:48:15 AM11/29/21
to Jochen Fassbender, skyind...@googlegroups.com

It definitely supports this format.  And it imports better than a regular cindex file.

Line by Line Indexing

unread,
Nov 29, 2021, 12:44:00 PM11/29/21
to SKYIndexUsers
Unfortunately, SKY 8 only supports ixml if it was purchased before a certain date unless Kamm changed that stipulation.  Maria–you might be one of the lucky ones to have that feature!

I have SKY 8 and I cannot use ixml files :(

But I love all of SKY 8's other features.  And I agree with Deborah, using xref instead of see also or see is a joy!

Michelle
Michelle Guiliano, DPM
PO Box 572 | Etna, NH 03750
(603) 277-0352
www.linebylineindexing.com
2021 Freelance Indexer Survey 

To view this discussion on the web visit https://groups.google.com/d/msgid/skyindexusers/07af01d7e530%242320c4e0%2469624ea0%24%40index-plus.com.

Maria Sosnowski

unread,
Nov 29, 2021, 6:33:02 PM11/29/21
to Line by Line Indexing, SKYIndexUsers

That’s fascinating, I had no idea!  I wonder why Kamm removed that ability?  Now I feel special!

 

Maria

Michael Wyatt

unread,
Nov 29, 2021, 9:49:06 PM11/29/21
to skyind...@googlegroups.com
The  User Guide says "The XML Records option is an advanced exchange
format that supports Unicode and is the preferred exchange format if it
is available. (NOTE: This option is only available if you purchased SKY
Index prior to May 1st, 2017 and has been replaced by the new IDEX index
exchange format.)" and "Index Data Exchange 'IDEX’ File – This is a new
specification developed by SKY Software specifically for the exchange of
data between indexing programs. This is the recommended format if the
program you’ll be exchanging data with supports it. This format retains
Unicode characters, character style, fonts, labels, and user create/edit
information."

However, the version of SKY that I have (8.0.13) unaccountably provides
both IDEX and IXML formats for both importing and exporting.

The IXML format was developed by the ecumenical Dave Ream who gained the
cooperation of all the Big Three and least one other third-party
provider.  The IDEX format was developed by Kamm and to my knowledge has
not been adopted by anyone else, which poses the question, "exchange of
data" with whom?

Michael


Reply all
Reply to author
Forward
0 new messages