[QUOTE=Ilajn;94200]Hi, I can't unzip this file. "Fehler 1 - der Vorgang ist nicht zugelassen." which means something like: Error 1 - this action is not allowed.[/QUOTE]

I have refreshed [URL="http://bit.ly/djsGUF"]the file[/URL]. (If there still seems to be a difficulty I will put it somewhere else).

[COLOR="White"]--[/COLOR]

[QUOTE=RobTrew;94201]I have refreshed the file. (If there still seems to be a difficulty I will put it somewhere else).[/QUOTE]

Extracts and runs here, at least. Interesting that the old zip file was 1 MB and the new one not even 1/10 of that!

[QUOTE=RobTrew;94201](If there still seems to be a difficulty I will put it somewhere else).

[COLOR="White"]--[/COLOR][/QUOTE]

No poblem: It extracts, now. Thank you.

Hello,

I'm back because things didn't improve. Another application on my phone may cause the problems with the messed up linkIds.

I tried OPML2OF on a document without links and linkIds. It still ends up in the former mentioned errors. I wonder wether it might be a problem that I didn't buy Omnifocus directly at Omni but in the App-Store (yes, it is the OS X application, I didn't install an iPhone/Pod/Pad version).

For testing I attach an example OPML file that doesn't contain linkIds.

You might be right about that — Rob's script had some instances where it referred to app id com.omnigroup.OmniFocus and that isn't correct if you have the OmniFocus from the App Store.

I made a version of the script that uses the other form of address. You can download it and try it out to see if it works any better: [url]http://dl.dropbox.com/u/971671/OPML2OF.zip[/url]

Let us know if that makes it work or not.

As a postscript, I have now amended the file to [URL="http://www.complexpoint.macmate.me/Site/Import_OPML_into_OF.html"]ver 0.6[/URL] which uses the form:

[CODE]tell application id "OFOC" -- OmniFocus[/CODE]

which should, I think, be compatible with Appstore-purchased and directly-purchased versions of OmniFocus, and perhaps even (touches wood) OmniFocus 2, when it comes ...

If Omni are using variant bundle-identifiers for all their AppStore versions, then there may be quite a lot of these edits to make. Apple was arguing when OS X 10.5 was released that the switch to the [I]id + bundle identifier[/I] form would be a good idea because developers were less likely to change the bundle name than the application name. This seemed to make sense:
[CODE]tell application "OmniGraffle Professional 5"[/CODE] for example, did look as if it might have a shorter shelf-life than:
[CODE]tell application id "com.omnigroup.OmniGrafflePro"[/CODE]
but 天有不测风云 (something like: 'the extreme sensitivity of non-linear systems to initial conditions makes them hard to model and predict' or just 'winds and clouds are hard to fathom' - though Google Translate offers a more extreme summary) and in retrospect it might have been more prudent to retreat to:
[CODE]tell application id "OGfl" -- OmniGraffle
tell application id "OFOC" -- OmniFocus
tell application id "OOut" -- OmniOutliner
tell application id "OPla" -- OmniPlan[/CODE]
etc, but this seemed a bit illegible at the time ...

[COLOR="White"]--[/COLOR]

[QUOTE=whpalmer4;94643]

Let us know if that makes it work or not.[/QUOTE]

Hooray! It works - unless the umlauts didn't import correctly. The source OPML file is in UTF-8 and e.g. TextEdit shows the umlauts correctly. I didn't find an option within OmniFocus to make it aware of UTF-8. May be I can use some text editor to work around this. But the less steps to perform the better it is. Is there a possibility to get the umlauts directly into OF?

It's the same with Rob's script OPML2OF ver 0.6.

[QUOTE=Ilajn;94665]Hooray! It works - unless the umlauts didn't import correctly. The source OPML file is in UTF-8 [/QUOTE]

Does the header of the OPML file specify UTF-8 ?

If not, it might be worth experimenting, in the script file, with changing the parse XML line, adding [I]encoding "UTF-8"[/I] at the end.

[QUOTE=RobTrew;94674]Does the header of the OPML file specify UTF-8 ?
[/QUOTE]

Is this first line of the file correct?

[CODE]<?xml version="1.0" encoding="UTF-8"?>[/CODE]

With this line I don't get umlauts :-(