Group items tagged

We noticed that because of the popularity of YouTube, the need for URL to MP3 converters has grown, and it’s much easier to find such a converter rather than a way to convert a video file to an audio one. … Continue reading →

We noticed that because of the popularity of YouTube, the need for URL to MP3 converters has grown, and it’s much easier to find such a converter rather than a way to convert a video file to an audio one. … Continue reading →

Learn how to convert PDF to Word online in just three easy steps

Converting PDF to Word is a great way to edit PDF documents just like any other text files. The main difficulty is to edit and, as we just found out, convert scanned PDF documents. We decided to figure out the … Continue reading →

Converting PDF to Word is a great way to edit PDF documents just like any other text files. The main difficulty is to edit and, as we just found out, convert scanned PDF documents. We decided to figure out the … Continue reading →

[This online tool allows you to convert a JSON file into an XML file. This process is not 100% accurate in that XML uses different item types that do not have an equivalent JSON representation. The following rules will be applied during the conversion process: A default root element is created JSON array entries are converted to individual XML elements All JSON property values will be converted to #text item types Offending characters will be XML escaped]

[This online tool allows you to convert a JSON file into an XML file. This process is not 100% accurate in that XML uses different item types that do not have an equivalent JSON representation. The following rules will be applied during the conversion process: A default root element is created JSON array entries are converted to individual XML elements All JSON property values will be converted to #text item types Offending characters will be XML escaped]

""…what this means is that the current safety standards as off by a factor of about 7 million.' Pointing out that a recent FCC Chair was a former lobbyist for the telecom industry, "I know how they've attacked various people.  In the U.S. … the funding for the EMF research [by the Environmental Protection Agency] was cut off starting in 1986 … The U.S. Office of Naval Research had been funding a fair amount of research in this area [in the '70s]. They [also] … stopped funding new grants in 1986 …  And then the NIH a few years later followed the same path …" As if all was not reason enough for concern or even downright panic,  the next generation of wireless technology known as 5G (fifth generation), representing the innocuous sounding Internet of Things, promises a quantum leap in power and exceedingly more damaging health impacts with mandatory exposures.      The immense expansion of radiation emissions from the current wireless EMF frequency band and 5G about to be perpetrated on an unsuspecting American public should be criminal.  Developed by the US military as non lethal perimeter and crowd control, the Active Denial System emits a high density, high frequency wireless radiation comparable to 5G and emits radiation in the neighborhood of 90 GHz.    The current Pre 5G, frequency band emissions used in today's commercial wireless range is from 300 Mhz to 3 GHZ as 5G will become the first wireless system to utilize millimeter waves with frequencies ranging from 30 to 300 GHz. One example of the differential is that a current LANS (local area network system) uses 2.4 GHz.  Hidden behind these numbers is an utterly devastating increase in health effects of immeasurable impacts so stunning as to numb the senses. In 2017, the international Environmental Health Trust recommended an EU moratorium "on the roll-out of the fifth generation, 5G, for telecommunication until potential hazards for human health and the environment hav

Working with various video formats can sometimes be a tricky task due to the large number of formats available today. All of them have their specific features and require all sorts of codecs for successful playback, editing, and other types … Continue reading →

Working with various video formats can sometimes be a tricky task due to the large number of formats available today. All of them have their specific features and require all sorts of codecs for successful playback, editing, and other types … Continue reading →

Read on to learn how to convert SWF to video formats like MP4 or MKV.

Keeping documents printed out on paper is a common way of storing them. However, if you need to somehow edit them, obviously you will need to transfer them into digital form. The best option here is to scan them and … Continue reading →

Keeping documents printed out on paper is a common way of storing them. However, if you need to somehow edit them, obviously you will need to transfer them into digital form. The best option here is to scan them and … Continue reading →

The OOXML <> XAML "fixed/flow" converter firs tappeared in the December 2007 MSOffice beta SDK. Now it's an easy to install MSOffice plug-in. So, where's that port of XUL to WebKit?

Project Description A Word 2007 Add-in that converts the Office Open XML (WordprocessingML) to XAML: For WPF, the document is converted into a FlowDocument element. For Silverlight 2 the document is converted into a StackPanel element containing TextBlock elements.

PDF is a widely-known format that is mostly used for storing documents. Editing such files is not that easy and quite often users tend to convert PDF to other formats like JPG, DOC, XLS and others thanks to their simplicity in processing. Icecream P…

PDF is a widely-known format that is mostly used for storing documents. Editing such files is not that easy and quite often users tend to convert PDF to other formats like JPG, DOC, XLS and others thanks to their simplicity in processing. Icecream P…

I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to

I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to

So now we learn some details about the new MS Office API(s) for unsupported file formats Microsoft promised a few months ago. Surprise, surprise! They're not for native file support. They're external process tools for converting to and from OOXML. That makes it sound as though Microsoft has no intention of coughing up the documentation for the native file support APIs despite its claim that it would document all APIs for Office (also required by U.S. v. Microsoft). The extra conversion step also practically guarantees more conversion artifacts. Do the new APIs provide interop for embedded scripts, etc.? My guess is no. There has to be a reason Microsoft chose to externalize the process rather than documenting the existing APIs. Limiting features available is still the most plausible scenario.

With great power comes great responsibility and with fast development of media technologies comes a wide variety of media formats. Each audio format has its own significant features: some maintain excellent quality, some offer compact size, some can be played … Continue reading →

With great power comes great responsibility and with fast development of media technologies comes a wide variety of media formats. Each audio format has its own significant features: some maintain excellent quality, some offer compact size, some can be played … Continue reading →

"If there was ever any doubt about whether Microsoft or Google would win the war of office suites, there should be no longer. Within the last several weeks, Microsoft has pulled so far ahead that it's game over. Here's why. When it comes to which suite is more fully featured, there's never been any real debate: Microsoft Office wins hands down. Whether you're creating entire presentations, creating complicated word-processing documents, or even doing something as simple as handling text attributes, Office is a far better tool. Until the last few weeks, Google Docs had one significant advantage over Microsoft Office: It's available for Android and the iPad as well as PCs because it's Web-based. The same wasn't the case for Office. So if you wanted to use an office suite on all your mobile devices, Google Docs was the way to go. Google Docs lost that advantage when Microsoft released Office for the iPad. There's not yet a native version for Android tablets, but Microsoft is working on that, telling GeekWire, "Let me tell you conclusively: Yes, we are also building Android native applications for tablets for Word, Excel and PowerPoint." Google Docs is still superior to Office's Web-based version, but that's far less important than it used to be. There's no need to go with a Web-based office suite if a superior suite is available as a native apps on all platforms, mobile or otherwise. And Office's collaboration capabilities are quite considerable now. Of course, there's always the question of price. Google Docs is free. Microsoft Office isn't. But at $100 a year for up to five devices, or $70 a year for two, no one will be going broke paying for Microsoft Office. It's worth paying that relatively small price for a much better office suite. Google Docs won't die. It'll be around as second fiddle for a long time. But that's what it will always remain: a second fiddle to the better Microsoft Office."

Google acquired "Writely", a small company in Portola Valley that pioneered document editing in a browser. Writely was perhaps the first cloud computing editor to go beyond simple HTML; eventually crafting some really cool CSS-JavaScript-JSON document layout and editing methods. But it can't edit native MSOffice documents. It converts them. There are more than a few problems with the Google Docs approach to editing advanced "compound" documents, but two stick out and are certain to give pause to anyone making the great transition from local workgroup computing, to the highly mobile, always connected, cloud computing. The first problem certain to become a show stopper is that Google converts documents to their native on-line format for editing and collaboration. And then they convert back. To many this isn't a problem. But if the document is part of a workflow or business process, conversion is a killer. There is an old saw affectionately known as "Reuters Law", dating back to the ODF-OXML document wars, that emphatically states; "Conversion breaks documents." The breakage includes both the visual layout of the document, and, the "compound" aspects and data connections that are internal to the document. Think of this way. A business document that is part of a legacy Windows Workgroup workflow is opened up in gDocs. Google converts the document for editing purposes. The data and the workflow internals that bind the document to the local business system are broken on conversion. The look of the document is also visually shredded as the gDocs layout engine is applied. For all practical purposes, no matter what magic editing and collaboration value is added, a broken document means a broken business process. Let me say that again, with the emphasis of having witnessed this first hand during the year long ODF transition trials the Commonwealth of Massachusetts conducted in 2005 and 2006. The business process broke every time a conversion was conducted "on a busines

"HandBrake is a tool for converting video from nearly any format to a selection of modern, widely supported codecs. Reasons you'll love HandBrake: Convert video from nearly any format Free and Open Source Multi-Platform (Windows, Mac and Linux)"

Alexandre Oliva Based on the widely-recognized and seldom-disrespected human rights to enjoy and memorize works of art one can access, and to grant and accept access to them, this article claims legitimate rights to preserve access to works, to convert works to different formats and media, to download and to upload works on the Internet, and to receive and to share works in P2P networks. The full enjoyment of these human rights amounts to self defense against the constant attacks to them.

[What is the "Invisible Web", a.k.a. the "Deep Web"? The "visible web" is what you can find using general web search engines. It's also what you see in almost all subject directories. The "invisible web" is what you cannot find using these types of tools. The first version of this web page was written in 2000, when this topic was new and baffling to many web searchers. Since then, search engines' crawlers and indexing programs have overcome many of the technical barriers that made it impossible for them to find "invisible" web pages. These types of pages used to be invisible but can now be found in most search engine results: Pages in non-HTML formats (pdf, Word, Excel, PowerPoint), now converted into HTML. Script-based pages, whose URLs contain a ? or other script coding. Pages generated dynamically by other types of database software (e.g., Active Server Pages, Cold Fusion). These can be indexed if there is a stable URL somewhere that search engine crawlers can find. ]