Posted by augsburgde on December 16, 2008 at 8:22pm
| Project: | Integrated Metatags |
| Version: | 6.x-1.0-beta6 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
have one more addition for that additional settings-page.
there should also be the meta-tag "content-language" - it tells the Searchbot in which language the content is available.
but the problem with this tag is that it looks like:
it' not built with name= but instead with http-equiv - http://www.submitcorner.com/Guide/Meta/language.shtml
if there is more then one language on a page it is comma separated:
http://www.seoconsultants.com/meta-tags/language.asp
Would be great if the module could work with the content translation modul of drupal core;
e.g. if you are surfing on an english page the content-language is set to en,
if you are surfing on an german page the content-language is set to de.
Comments
#1
I agree. The user should be able to pick between the 'name' or 'http-equiv' (besides the 'content') attributes. The 'http-equiv' attribute may hold many different values, such as: "Expires, Pragma, Refresh, Content-Type, Content-Language, Content-Style-Type, Content-Script-Type, Page-Enter, Page-Exit, Site-Enter, Site-Exit". Just to name a few. ;-)
#2
Wow, I'm having flashbacks to Eaton's Building APIs session this morning... I'll take a look at it, but if it will require a lot of time to do, it might have to wait until v2.0.
And I'm going to change its priority from "critical", but thank you for the feedback and enthusiasm in helping make this module better!
#3
A quick and dirty patch has been attached. In the user interface add http-equiv= to the static or dynamic names. E.g.
Example for static:
http-equiv=Content-Language|[language]
http-equiv=Content-Script-Type|text/javascript
http-equiv=Content-Style-Type|text/css
The patch recognizes that the name start with http-equiv, strips it of the name, and outputs http-equiv="..." instead of name="...".
Patch has only been tested in Drupal 6 (not thoroughly) and is not a hint towards a definitive solution, though I think it could be used for static tags. Something like attribute-name:attribute-value|content-value with the attribute-name: part being optional (and defaulting to 'name'). For dynamic tags I would opt for an additional input field.