|
|
| Line 1: |
Line 1: |
| <tabs> | | <div class="row"> |
| <tab name="Foo">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</tab>
| | <div class="large-3 columns"><evlplayer id="player1" w="260" h="360" service="youtube" defaultid="aXrVDx8f-TE"/> '''07 May'''</div> |
| <tab name="Bar">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</tab> | | </div> |
| <tab name="Baz">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</tab>
| | </div> |
| </tabs>
| | <br /> |
| | | <div align=center> |
| ########
| | <div class="row"> |
| Questions / Issues:
| |
| - What kind of storage is used for verses? (database / text files)
| |
| - May i program in PHP and MySQL?
| |
| - The Vedabase only seems to search Sanskrit, wheres VM would like to see translation search as well: so we have Sanskrit / WBW / Translation?
| |
| - Visnu Murti explained me that the main "entry point" for the search will be the word-by-word translation, and also that the search will comprise either Sanskrit or English (or any other language). But of course it should also be possible to type a specific word (or pattern: see Vedabase), not present in the word-by-word, but present in the (Sanskrit) verse or the (modern language) translation ==> should we compile all word tokens (from verse/wbw/transl) or just those from wbw?
| |
| ;
| |
| - low level / high-level search logic
| |
| ; high: for instance SQL expression with WHERE clause that queries records(not maximally efficient)
| |
| ; compute some kind of jump-table or ATN or DAG / proces a token list of all verse/wbw/transl
| |
| - if you start with a word from the wbw and choose for the "begins with" or "ends with" option, you have to look in the verse-lines, and the token might be different (how to solve?) ==> for instance "tadocyate" BG 2.55 is combination of tadā and ucyate (but in Vedabase searching 'ucyate' has an empty result)
| |
| - abstraction from diacritic signs ==> a should match a with line above it / n should match n with dot below it
| |
| (encoding UTF / Unicode)
| |
| ########
| |
| This is my Vaniseva notepad. I can write whatever i like. I should remember that it is a public document. I should not put active category links here.
| |
| | |
| Forced line breaks: See ES/SB_2.2.30 (is like Spanish text, but original English text has different solution - with extra blank line / i prefer the forced line breaks) ===> Vanipedia standard prefers lines not too close together / we do not have to stick to the PDF text
| |
| | |
| Usage of « instead of " in ES translation (see for instance 'end of chapter' trext)
| |
| | |
| Italics in 'end of chapter text':
| |
| | |
| 1.10.36 (ES) = (no italics) Así terminan los significados de Bhaktivedanta correspondientes al capítulo décimo del Canto Primero del Śrīmad-Bhāgavatam, titulado: «La partida del Señor Kṛṣṇa para Dvārakā». <br>
| |
| 1.10.36 (EN) = (italics) Thus end the Bhaktivedanta purports of the First Canto, Tenth Chapter, of the Śrīmad-Bhāgavatam, entitled "Departure of Lord Kṛṣṇa for Dvārakā." <br> ====> should be italics and extra line
| |
| | |
| ==> i think italics should be forced here by surrounding the line with \'\'
| |
| | |
| NB point should not be part of chapter title in 'end of chapter text' <br>
| |
| -- 2.1.39 (ES) Así terminan los significados de Bhaktivedanta correspondientes al capítulo primero del Canto Segundo del Śrīmad-Bhāgavatam, titulado: «El primer paso en la comprensión de Dios». <br>
| |
| -- 2.1.39 (EN) Thus end the Bhaktivedanta purports of the Second Canto, First Chapter, of the Śrīmad-Bhāgavatam, entitled "The First Step in God Realization." <br>
| |
| | |
| NB inconsistent use of italics and extras empty line (sometimes yes / sometimes no): <br>
| |
| ES/SB_1.1.23 <br>
| |
| ES/SB_1.2.34 <br>
| |
| | |
| See SB_1.13.37 : Spanish PDF contains footnote in purport: Ese es el veredicto del Gītā y del Bhāgavatam.** <br>
| |
| The problem is that the footnote at the bottom of the page does not show properly because ** at the beginning of a line is interpreted as indent bullets <br>
| |
| In the English original they forgot all about it and in the Vedabase the link does not work <br>
| |
| Special case of double notes: see SB_2.3.19 (NB: the English original only has one note!)
| |
| | |
| What to do with footnotes? See for instance ES/SB_2.3.14 "... de vuelta a Dios*" (English version uses *** which i think is too heavy --> what to do if there more than 1?) <br>
| |
| I decided to insert a space before the * sign [===> ask Sahadeva why 3 stars? / extra space is OK
| |
| | |
| BUG: The compilesb page does not remember the chapter (it only remembers the language, the canto and the verse number in the list boxes)
| |
| | |
| BUG: the following leads to a hyphenation error message when pressing "create page" button (ES/SB_2.3.22), colons before each line ==> has to with - after 'nana'
| |
| :śrī-vigrahārādhana-nitya-nānā- <br>
| |
| :śṛṅgāra-tan-mandira-mārjanādau <br>
| |
| :yuktasya bhaktāṁś ca niyuñjato ’pi <br>
| |
| :vande guroḥ śrī-caraṇāravindam <br>
| |
| | |
| NB: capitals sometimes disappear in copy-paste from translation in PDF document (Vyāsadeva, Śukadeva Gosvāmi, Mahārāja Parīkṣit, Vasudeva, Personalidad de Dios) <br>
| |
| NB: copy-paste function removes hyphens at end of line, but ... sometimes they are part of the word!!! (nairguṇya-sthāḥ -> nairguṇyasthāḥ), see for instance 2.1.34 = ambu-vāhān—las nubes (becomes ambuvāhān—las nubes) <br>
| |
| it also happened in the 1st Canto 1.2.17 ==> "svakathāḥ—Sus propias palabras" (should be "sva-kathāḥ—Sus propias palabras") <br>
| |
| it also happened in the 1st Canto 1.3.4 ==> "bhujaānana—manos y caras" (should be "bhuja-ānana—manos y caras") <br>
| |
| it also happened in the 1st Canto 1.3.42 (probably extra space added trying to fix it) ==> "mahā- rājam—al emperador" (should be "mahā-rājam—al emperador") <br>
| |
| (checked until 1.3)
| |
