Closed (outdated)
Project:
Bibliography Module
Version:
6.x-1.7
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
8 Nov 2009 at 09:05 UTC
Updated:
21 Dec 2018 at 15:19 UTC
Jump to comment: Most recent
Comments
Comment #1
rjerome commentedThis is generated by the theme_biblio_alpha_line() function in the biblio_theme.inc file on lines 1023 to 1030 like this...
If you were to wrap the "chr($i)" calls in t() then add the letters A thru Z to your translation file it should work. So you new code would look like this...
Let me know if this works and if it does, I'll put it in the code.
Ron.
Comment #2
perfectsense commentedSorry, i can't understand that. My translation file (biblio-6.x-1.7.ru.po) contain strings like this:
and not contain any alphabet symbols like ABCDE...
Where can i add letters A thru Z ?
Comment #3
rjerome commentedThis is probably not the best way to do this, but lets just call it a proof of concept...
you would have to add (at the end of the file) lines like
.... and so on for each character, but I guess this might not be the best solution since there is not a one to one correspondence between the Latin and Cyrillic character sets.
Comment #4
perfectsense commentedNo, it's not working. When i insert this code:
i see only blank screen in Firefox and error 404 in Opera.
Comment #5
rjerome commentedOpps, I hadn't actually tried that code, but it looks like there is a syntax error in the second "$output .= " line, it should be
Comment #6
perfectsense commentedYes, it's working. But this:
is too bad. (((
Thank you very much.
Sorry, can i ask you another question? Is there a way to place index with two rows of letters? like this:
ABCDEFGH......
АБВГДЕЖЗ.....
Comment #7
rjerome commentedI'll see if I can come up with a more elegant solution which includes all Cyrillic characters.
Did mean that you want to have both Latin and Cyrillic lines?
Comment #8
perfectsense commentedYes, both Latin and Cyrillic lines. Thank you.
Comment #9
liam morlandThis version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.