Closed (outdated)
Project:
Link
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Anonymous (not verified)
Created:
17 Feb 2009 at 00:08 UTC
Updated:
31 Aug 2024 at 10:54 UTC
Jump to comment: Most recent
Comments
Comment #1
no2e commentedI want this too.
Especially for hreflang and title attributes.
Or offer "harcoded" fields for valid attributes (hreflang, lang, title, rel, rev, …) and an additional text field for custom attributes.
Comment #2
jcfiala commentedWell, you'll be happy to hear that 'title' can now be set in the field settings page, in the current devel branch. So you'll get that soon.
That said, hreflang is apparently referencing the target of the link, and so can't be handled so easily... Hm.
I don't want to allow just any text to be entered when a link is being created, because of the possibility of wierd values. Do you know of anywhere in Drupal where the possible languagecodes are available? One idea that comes to mind is a switch on the field settings page that would allow for a dropdown of different languages to be displayed on the node form, where the user entering the link could set the language there.
Thoughts, ideas?
Comment #3
ssm2017 Binder commentedthe language code can be accessed with the $_GLOBALS['language'] object :
http://api.drupal.org/api/global/language/6
but i think that you would need to get infos about i18n too (i never used it)
Comment #4
doublejosh commentedYou may want to include in your example on the project page what is necessary to preserve the attributes...
Placing it within a link function call might be good as well.
Comment #5
mgiffordMaybe this could be done for the D7 version and then back-ported to D6.
I was going through this blog post on multi-lingual accessibility and started thinking about adding in hreflang attributes.
Works well in both HTML4 & HTML5, but it doesn't seem to be used all that much in practice.
Comment #6
dqdI'll close this issue due to inactivity for 14 years and upcoming EOL of Drupal 7 in January 2025. While the project version for Drupal 7 will keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. Thanks for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority to "Critical" here.