Download OpenXML Viewer Command Line

0 views
Skip to first unread message

Vida Hubbert

unread,
May 20, 2024, 5:36:24 PM5/20/24
to vipaphosfern

Assuming you wish to parse the actual XML inside a SOAP-envelope/package, you may do that by using PowerShell - if you instead wish to parse the actual SOAP-data you will need to consume it via a worker in a higher language, I am not aware that this is possible via PowerShell.

Another option is to make windows open the file with the default xml viewer. Lets say Internet Explorer is your default xml viewer, the following command will start Internet Explorer, open the XML file and switch to it. You click the x and you return to the commandline program (unless you switch to other applications)

download OpenXML Viewer Command Line


DOWNLOAD 🗸🗸🗸 https://t.co/pGtZW0yZtr



I personally think start is the preferred mode, because the default xml viewer will have syntax highlighting, where the command window does not, but if the xml file is very small and you want to quickly look up a text, copy that and use it in a new command, then the type command will be preferred.

If the file is an XML table, you can open it in LibreOffice Calc through the Data > XML Source menu1. Inside it, you just need to open the XML file, point to the table you're importing on the left column and specify a destination in your sheet in the right text field. Example:

BaseX is a very fast and light-weight, yet powerful XML database and XPath/XQuery processor, including support for the latest W3C Full Text and Update Recommendations. It supports large XML instances and offers a highly interactive front-end (basexgui).

In case you don't succeed with LibreOffice, try using SoftMaker FreeOffice. This free office suite has much better import and export filters that let you run Microsoft Office formats faithfully. The whole office suite is feature-packed, but needs only 58MB. It's well coded, very fast and reliable. Here's the link where to get it:

This is a command-line tool which can select data from an XML file on the basis of the types of elements and the values of their attributes or those of related elements. I am not sure if it is easy to generate a CSV file or other suitable for loading into LibreOffice (if that is your aim), or whether you would need to transform it a little first. (I shall try to remember to update this if I find out more.)

The examples given in the Wikipedia article (link above) show the command as xml (e.g. xml sel for a selection), but in my case (OpenSuse Leap) it is xmlstarlet, which is also the package to install; I do not know what the situation is for Ubuntu.

XML Copy Editor (xmlcopyeditor) is a fast, free, validating XML editor. It features DTD/XML Schema/RELAX NG validation, XSLT, XPath, pretty-printing, syntax highlighting, folding, tag completion/locking, and a spelling/style check. XML Copy Editor can be installed from the default Ubuntu repositories.

Are there any other way of creating PDF's from Progress than PDFInclude? We've used PDFInclude successfully for simpler PDF's but when we start working with things like templates its not working that good.

Not sure if it is... The original question was if there's a solution for creating PDFs from Progress (not ABL). One of the good things using Progress is that it's open enough to talk to most 3rd party software.

I had a quick look at the Java component Doug mentioned. Looks like it can be using with Progress in a number of ways (i.e. running the JRE as a command line tool, posting an XML to a web service etc.).

Its ideal for using Word or Excel or other as the WYSIWYG slash design tool and filling the form with 4GL (just inserting or replacing the custom data XML file) and doing it all on UNIX, Linux or other.

Growing and widespread support, MS Office 2000 or better, Open Office, Star Office, Lotus you can even open an OpenXML file in your iPhone. Not to mention OpenXML to other file formats conversion utils.

It is clear from prior exchanges that you are a very "enthusiastic" person, Alon ... a quality which I appreciate since I can be very enthusiastic myself on a number of fronts. Which said, I think that one has to understand that, whatever the virtues of other technologies, there is a certain attraction to PDF for two really big reasons. One is that it is THE dominant technology for distributing formatted documents to people who have unknown document viewing technologies. ... if you are on the internet and reading anything, you almost certainly have PDE reader installed. Secondly, it tends to be a defacto read only technology. For most purposes ... e.g., sending someone an invoice or statement ... you really have no interest in having the recipient edit the document. Oh, perhaps 1% or less of the time there could be a reason for a computer-knowledgeable person to add comments to to a disputed invoice but if you consider that only 1% of the invoices are likely to be disputed and only 1% of the users who get invoices they want to dispute, that's a really, really small percentage of cases where being able to edit is a virtur.

So, whatever attraction some of these other technologies may have in terms of document sharing where there are multiple contributers to the same document ... those virtues are not necessarily real virtues if one wants the document to be read only and to be readable by anyone without having to get software specific to the source.

Theres free viewers, some level of support for the old binary formats in other office suites and now that the new formats are standardized and well documented wider and growing support in office suites, utils etc.

But overall its a richer format with much more possibilities and because of the clear data presentation separation it is very suitable for working with forms and complex forms among the other possibilities for working with documents.

Actually I think the discussion about various XML formats should be handled elsewhere. I posted here with a specific question and that was how to create PDF's. If PDF's are dated or not isn't really the question.

Progress, Telerik, Ipswitch and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Microsoft Office 2007 came out about a year ago. Have you yet started getting .docx, .xlsx, or .pptx files? Whether you are an OpenOffice.org user or a Microsoft Office 2003 user, you are probably frustrated trying to find some way to convert, import, or otherwise open these documents.

These new document formats are called Office Open XML, OOXML, or OpenXML. They are significantly different from the Microsoft Office 97, 2000, 2003, or XP formats. The new formats are based on XML while the old formats are binary.

If you don't use Linux or you are afraid of the terminal, skip to the very end. Otherwise here is one easy way to convert these documents thanks to Novell. They developed a tool called the OpenOffice OpenXML Translator, and soon it will be fully integrated into the mainstream OpenOffice.org.

Because this procedure is for the command line (and does not directly integrate into the vanilla OpenOffice.org), this procedure is well suited for automated, batch conversions between OpenXML and OpenDocument Format. This procedure should work on all Linux distributions: Ubuntu, Fedora, SUSE, Mandriva, Debian, and so on.

The general idea is the same no matter which Linux distribution you use. You are basically copying one file out of the RPM as if it were a tarball or a zip file. You are not installing the RPM in the traditional sense, so don't worry if you run a non-RPM-based system such as Ubuntu, Debian, or Slackware

For more help on arguments, just run OdfConverter without arguments. If you are curious, there are some OpenXML sample documents included in the RPM: check the directory usr/share/doc/packages/odf-converter/.

thanks to everyone's help (especially jeremo's follow up) I was able to get this running on Ubuntu as well...turns out google-earth had libtiff.so.3 and i just copied it into /usr/lib ...don't get confused when you run OdfConvert and it doesn't work, it's "OdfConverter" :)

Mathematical equations are not
translated.


Hello, I wrote a ODT file, containing enumerated list, tables colors and mathematical formula. I converted it to docx format.

- I could not open that file with the Oygen Openoffice which contains a docx import filter, files corrupted.
- converted the docx file back to odt, but then the math formula were gone.

can anybody comment on this?

Thanks a lot, this is REALLY helpful. I was using zamzar to convert and that works but is slow with the free account.

One suggestion to make it easier. If you prefer GUI rather than CLI you can right-click on a docx file and say "open with" then choose custom command. For the custom command type "OdfConverter /i" After that you can go to properties of any docx file and go to the "Open With" tab and choose OdfConverter as the default program. From now on, when you click to open a docx it will not open it but will instead spit out a odt file in the same directory which you can open. This works well in Gnome/Nautilus. I am sure the instructions are slightly different in KDE/Konqueror.

Is it necessary to have openoffice installed on the system before using OdfConverter?
I am able to convert pptx into odp's but the output is not good enough i.e. in lots of slides TEXT in the slide is getting clipped.
So is OdfCoverter somehow dependent on OpenOffice i.e. some schema files, it looks for in oo installation directory?
Thanks!

dmk: I was thinking of something like that, and you encouraged me finally to do it. Check out odf-converter-integrator which should be usable in the next few days.

bhups: odf-converter is completely independent of OpenOffice.org, and you can use odf-converter if OpenOffice.org is never installed. Check odf-converter on how to report a bug

A cool thing this converter :) . BTW, in your guide you're mentioning "OdfConvert" instead of "OdfConverter" command. I spend a few minutes figuring out what's the problem with the command:).

Tried with SuSe 10.1

dd60e6d636
Reply all
Reply to author
Forward
0 new messages