On Fri September 24 2004 15:23, s. keeling wrote:
> Incoming from Curtis Sloan:
> > However, the notes in korganizer still don't respect the \n.  Any leads
> > to solving that would be great.  But I think I'm pretty close now.  I
> > still need to evaluate each DESCRIPTION property for some rogue
> > characters that need escaping.  Thanks to everyone for their help so far,
> > especially Stephen.
>
> Glad to see you're making progress.  :-)
>
> I don't use korganizer (nor any other kind of organizer; I do better
> with find and grep :-), so I have no idea what the file format should
> be.  Can you set your current data aside and make korganizer save a
> sample data file?  That should make for a good comparison between the
> two, showing you what you need to do with the real data.

Heh, yah I don't know why I didn't think of that sooner.  I set aside a sample 
from the .nocr file and imported it.  I made a copy of the imported sample 
before modifying it (for posterity), and then I formatted it to how I 
eventually want it in korganizer.  This way I had three samples to check -- 
the original, the imported and the modified.  I checked for differences using 
'od -c' (thanks for that! ;-).

<rant>

Although I don't know anything about standards for text formats, it appears as 
though korganizer simply has some wild (I would guess non-standard) ways of:

1)  importing text
2)  storing text

Grrr.

1)  There are extra \n's added to the DESCRIPTION property when the text is 
imported -- and for no apparent reason since the placement seems arbitrary 
and they're not even respected by korganizer.  Why would a program not parse 
its own modifications?!  I guess no one ever said that KDE-PIM's import 
filters were perfect.  ;-)

2)  The \n has to be exist as actual characters, not as control data (e.g. 
literally, "I want a newline here\n".  I think I've seen other KDE apps 
behave this way as well.  If any KDE developers would like to comment on why, 
I'm all ears.  ;-)  LOL

</rant>

At least I now know what all the modifications are that need to take place to 
format the text as I'd like (and all this for my stinkin' Palm that will 
probably truncate it!  LOL  ;-).

And thanks to Stephen for his example script (I always need an example script 
to hack for myself :-P) I can probably automate the modifications in at least 
one language.  ;-)

I can't be too far off now, and I'll be rid of the reboot forever!  Okay, 
maybe not forever (I'd like to be able to install Palm stuff to my SD Card 
under Linux ;-).  But I'll be one (big) step further away.  :-)

Thanks for everyone's help!

Sincerely,
Curtis

P.S.  FWIW, here is the only reference to this problem I've come across so 
far.  It's relatively recent, and no apparent solution has been proposed.

http://lists.kde.org/?l=kde-pim&m=106807189903808&w=2

OTOH, I highly recommend Outlook2vCal for helping to cut ties with 
Microsoft!  ;-)

_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca

Reply via email to