1. Don't hard-code URLs in translation strings

In the large majority of cases, you should never hard-code URLs in translation strings. Use the variable

[[aopts]] ('aopts' => “href='$LJ::SITEROOT/page/'”)

instead. This way, URLs can be changed (in the code) without having to worry about translations needing to update their strings to get the new URLs.

Exception: If a string is on a generic livejournal page but needs to link to a site-specific page, then the string without the link should be in en.dat, and the string with the hard-coded URL link should be in en_XY.dat (to avoid putting links to site-specific pages in generic livejournal pages).

For example, there may be a feature that is only available to paid accounts on LiveJournal.com, and a string on a livejournal page that says this. So, in en.dat, the string would be something like, “This feature is not available to your account type.”. In en_LJ.dat, the string would be something like, “This feature is only available to <a href='http://www.livejournal.com/paidaccounts/'>Paid Accounts</a>.” When the code makes it possible, it's a good idea to use <?siteroot?> instead of, for example, “http://www.livejournal.com/”, so development environments can get links to local pages and not those on, for example, LiveJournal.com.