Hi Roland, On 1 Oct 2014 at 15:51:05, rol ([email protected](mailto:[email protected])) wrote:
> Hello, > > Thank you for your answers. It then makes sense that embedding content in a > CDATA block is not a good idea, > since that would have to be done not only for the content element, but for > all metadata elements that might contain > xml-encodable characters. > > I forgot to say: The input files are in Trac format ( > http://trac.edgewall.org/wiki/TracWiki ) so if there exist > a conversion script that takes a set of trac files and generates an XAR > archive I would happily use it. > > In an older thread I found this: > > > Could you tell us more about the wiki you wish to convert since there > are some > > conversion scripts that exist already on http://code.xwiki.org and in > the > > sandbox. > > But that resource has either been moved or is deleted. code.xwiki.org has been moved to http://extensions.xwiki.org Actually I’ve put a link to all extensions related to migrating from one wiki to another here: http://platform.xwiki.org/xwiki/bin/view/Features/Imports#HImportingfromanotherwiki AFAIK there’s no Trac import ATM but maybe Trac can export in HTML and then read that in XWiki. Alternatively use some regex to convert as some scripts do... Hope it helps a bit, Thanks -Vincent > If there is no existing script for importing a set of Trac wiki files, I > will go for building a XAR archive, > since my earlier problems with that turned out to be the same encoding > problem that I had with the REST import. > > Is there any published schema of the xwikidoc document type (or a list of > optional fields), and maybe also a description of the package.xml? > > If not, I will just tweak it from an example export. > > Thanks, > Roland > > > > > ----- > Roland Hedayat _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
