Open drdhaval2785 opened 7 years ago
Something like Panini Ashtadhyayi app.
Take a look at purANa encyclopedia file and you'll see links like: <a class="pe_a_pada" href="पार्वती">pārvatī</a>
Yes, we can add hyperlinks. , and we can use html for linking, divison, redirection, organising. to enable html tags in compilation, we have to add fallowiong lines at starting of babylon file.
`#stripmethod=keep
` book name is the name which we want to appear in golden dict. after those three lines, one empty line, and then remaining entries. (as in vedicindex.babylon file). if we add them, compiler will keep all html tags we used in babylon file.
Now to add hyperlinks, we can add just like in html, like <a class="sk_hyperlink_internal" href="HEADWORD">DISPLAY_TEXT</a>
.
here HEADWORD should be the one of the head words of destination. i.e. like "6.1.904" .
for example if we have entry like
అనంత|ananta|anaMta|anMtaM infinite in telugu. used with pratyaya 'mu' or 'M' in general
then we can use any of head words in link which points to this word.
<a href="అనంత">ananta</a>
, like that. display text can be what ever we want to display.
If those terms are too generic, and may give results from other dictionaries too, we can give an id for all words in headwords, which are not actual searchable pattern but unique id for linking. like fallowing.
అనంత|ananta|anaMta|anMtaM|SK@WORD119 infinite in telugu. used with pratyaya 'mu' or 'M' in general
above SK@WORD119 is given as headword, which we are sure that maynot be used any other dicts. so we can link to this word from anywhere like follow
<a href=" _SK_@WORD119">ananta</a>
then it will only give exact this word, with out remaing entries from other dicts.
As of now, I feel that adding HTML markups did add to clumsiness. Will defer it till more appropriate time.
If those terms are too generic, and may give results from other dictionaries too, we can give an id for all words in headwords, which are not actual searchable pattern but unique id for linking. like fallowing.
Dhaval, why not?
adding HTML markups did add to clumsiness.
Only for coder, not for the user. User above all, Dhaval!
Only for coder, not for the user. User above all, Dhaval!
Thats the precise reason. HTML had a lot of disgruntled users. Txt is hot cake. In HTML different applications render differently. Desktop units do render them well and mobile units throw a lot of styling junk, making it unreadable.
mobile units throw a lot of styling junk, making it unreadable.
Screenshot proof?
In colordict for android, textview shows this junk. Only textview has some kind of hyperlinking shown. webview doesnt even have hyperlinks. It doesnt have this styling remnants, but doesnt do anythin useful.
@drdhaval2785 - I am a bit skeptical. The screenshot you show above is not simple html - it includes wasteful css. I don't think just adding anchor links will make things go bad. Please do a test.
There are a lot of references in SK where the commentary refers to another rule in SK. Is there a way in which they can be linked in stardict format?
E.g
Here 69, 86, 97 etc are references and are properly marked with markup. Is there a way by which they can be converted to clickable items which open those particular entries in SK.
Whats your take @damooo?
Nyasa also has similar references in brackets. This feature will open up a possibility of better linked commentaries.