Re: Some Interesting Data On Websites Designed With Xara
My understanding of the CMS Versions, Major and Minor is the XARA HTML generator, c.f., <meta name="Generator" content="Xara HTML filter v.9.6.1.39"/> for v17.0
v10 has generator version 7.0 and Xara Xtreme 5.1 is version 2.2 (<meta name="Generator" content="Xara HTML filter v.2.2.0.675"/>).
CMS has nothing to do with actual content management systems but
Quote:
A CMS will sometimes include a meta tag within the html of each page. This is usually a "generator" tag like <meta name="generator" content="What CMS" /> but could also be "application-name", "Powered-By" or anyting else the CMS creators decide to use.
This is the more telling as it shows how much Xara loses against each version it delivers.
Map generator version to product version and you can see the trend.
Acorn
Re: Some Interesting Data On Websites Designed With Xara
Re: Some Interesting Data On Websites Designed With Xara
Quote:
Originally Posted by
pauland
Don't let us stop you.
Before any bright spark ( USA: Smartass ) also volunteers that you can buy a domain for any country from any other country, I already know.
I made my comment with regard to the balance of the distribution, which will generally reflect the balance of the location of the web designers, but not perfectly, as has been pointed out.
dont you just love the way irony provokes ;)
what I want to know is.. so what? if that is the way the stats are, so what? should anyone in the know actually be surprised
Re: Some Interesting Data On Websites Designed With Xara
Once again I'm totally confused. Not unusual. This site seems to search for sites using CMS software. The majority of Xara created sites never use CMS, perhaps apart from those created via xtom . So what use is this data?
Re: Some Interesting Data On Websites Designed With Xara
Quote:
Originally Posted by
Egg Bramhill
Once again I'm totally confused. Not unusual. This site seems to search for sites using CMS software. The majority of Xara created sites never use CMS, perhaps apart from those created via xtom . So what use is this data?
Egg, read my last Post. CMS is a listing of what the developer puts in the META data as "generator. Xara's generator is the Xara HTML filter, which has it own version number different to the product version number. This site is simply recording what the published Xara sites were published with.
Know the generator version, know the product version.
For example, your recent website is:
parkeston.com/tim-box-2/ uses
Category |
Software |
Version |
CMS |
Xara |
9.6.0.33 |
Web Server |
Apache |
So you were using XDPXv17.0.
Clearer?
Acorn
Re: Some Interesting Data On Websites Designed With Xara
Quote:
Originally Posted by
Egg Bramhill
Once again I'm totally confused. Not unusual. This site seems to search for sites using CMS software. The majority of Xara created sites never use CMS, perhaps apart from those created via xtom . So what use is this data?
CMS systems tend to insert meta data into the hTML that identifies the site as having been generated through software rather than being a static, hand-coded site.
The Xara software inserts some generator strings and the and CMS site thinks Xara sites were created from a CMS.
So, in short it finds Xara sites whether they have used a CMS or not.
Re: Some Interesting Data On Websites Designed With Xara
Duplicate Posting after an Internet outage - IGNORE.
Acorn
Re: Some Interesting Data On Websites Designed With Xara
Aha, "HTML that identifies the site as having been generated through software.....," that clarifies matters. Thanks for that, Pauland.
Re: Some Interesting Data On Websites Designed With Xara
Quote:
Originally Posted by
handrawn
dont you just love the way irony provokes ;)
Err.. no
Quote:
what I want to know is.. so what? if that is the way the stats are, so what? should anyone in the know actually be surprised
Too much cleverness for this poor soul.
Time for Summer Recess.
Re: Some Interesting Data On Websites Designed With Xara
@ Acorn
As mud!
Where do you get the Category = cms from? I can't see it in my page source.