Post reply

Name:
Email:
Subject:
Tags:

Seperate each tag by a comma
Message icon:

Anti-spam: complete the task

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Johann
« on: July 13, 2018, 04:28:32 PM »

a Haa... that solves much (one each page has its heading for friendly displa Configuration Setting: useheading and IndexMenu Plugin for not needing to edit the indexes (possible, just would not give corresponding accesslink to the public tipitaka.org pages). Atma installs it for testing, assuming its welcome and given.

A sample of this index is now put on http://accesstoinsight.eu/doku.php?id=cs-rm:index#index

The use heading opinion nicely displays the title names now, will filenames (in code) are matched as fine selection as when typed into the search box.

Still a combination of both to display would be fine.
Posted by: Johann
« on: July 13, 2018, 08:43:38 AM »

Useally my person does things 2, 3, 4 times from the begining again. Vision in mind, then still lacking this or that, yet not perfect.

The second question is particulary reflected in the first. And if having later 2100 file and wishing to put them on their places, morits would see why.

And thats also for the brain. Some might know mn001 , that it is in the Suttapitaka, in the first vagga. But if having a file called bhu001 one would have problems.

Now one could give them a real name only. karanayametta sutta So, knowing the name, would you know which pitaka, nikaya, vagga and subvagga it belongs?

Therefor both useful systems, that of "modern" codes from ATI (western focus is on suttas and ends there) and the tree from the edlers by names.

that is why there came {pitaka}.{nikaya}.{vagga}.({subvagga}).{sutta no.} as for the filename into being.

If searching for an01.001, by the surfix _{att/tik/any} on matches them well in the preview putting the letters into the search box. On the other side, if searching via sidemap it's fine as well.

This works all fine till atthakatha Abhidhamma and parts of tika. When coming to anya it's no more that clear executeable and Anya it self contains already double and tripple naming. A certain collection has the first book and the first chaper with same name containing things not clear a counterpart of the tipitaka.

Till today, and actually having spend 100's of hour on trying to sort in fine, may person came till abouf jataka to be sure that the system would not run ugly of build on a not suitable structur.

Now this here, my person guesses, since not even abhidhamma (horrible structur) has been sorted well in the west, is the first time after tipitaka.org (which used a simple but not asumesable code and indexssystem for a stabil not dynamic storing, yet hard to find anything if not a little familar) that the whole heritage of the Sanghayana get's sorted.

It's all looked simple for my person as well. Then after you developed structure for the fist and second level, after the 10 file you match a new vagga/subvagga structur... Since from jakata on there is since longer no much broad interest, Anya is like the book shelf in a studend room and not like a chemist register.

Practical Anya:

Caturārakkhadīpanī is a book under the collection Nīti-gantha-saṅgaho in Anya-Commentaty and contains serial book. Within the is the Caper Kāyapaccavekkhaṇā which is the actual file (pagename)

To come to it one follows the indexes (pagenames under the namespace tree calked index) one after another or more direct, since the fist index contains already the whole structur. Thats right, sub indexes are not really necessary if the fist already contains the whole.

So it has more practical reasons. For example think on an, mn, iti. If knowing the system of the Sanghayana one knows that iti is a subvagga of kn. Same counts danger counts for mn. there is no mn123 in the sanghayana edition. It came from many people focusing on a certain levels "gemeinsames vielfaches).

Now, for example, if on works out Visudhimagga the first book, he might expand the capters index and if finished, might copy it into the index of visudhimagga, even to the anya index. Another might work from another level...

It means it has been the result of practical work in the worst situation of knowing the whole of particalar parts. Since it will stay dynamic, the further levels indexes have been not deleted (like cscd) but serve 2 purposes easy to acces in both directions, on which level ever one might enter, and to focus on a scale suitable to ones concentration and reminding and then put it together upwardly, downwardy.

Thats why this system from of pitaka, nikaya, vagga has been keep here as well and the structure is either by name flat (aside anya for all files) but also physical in levels, not only presented by a digital tree like the xml in cscd. If looking on the flat system of cscd one will fine att file codes in the tipitaka and so on. Meaning that even this simple system runned out ugly after finding out detail from the elders.

Further, the middle placed indexes are thought to get enriched by single chapers within one file (anchor content #v1...v5) and the deepes would contain later also the single suttas links (anchor #s001...s057) of the files. Meaning getting a zoom level by level. For one index that becomes to large.

But as told, open to others as well. Just knowing that it can serve for "headage" for weeks and month, yet next day finding out... "ok, again from the beginning". It's like doing/training Jhana, mastering the worlds.  :) That is why doing = sacrify has it's benefit = having learned a skill.

So know that Nyom has to structer something that probably nobody knows as a whole in it's various details and structur. It needs to be open in that far and "nachvollziehbar" for others, as well as accessable for people coming from differen learnsystems. West does not know the way of the elders and elders do not know the code-thinking of western.

For example look at ATI where it ends and beginns to go astray of suttacentral, having trouble with vinaya and abhidhamma and possible no logical way to ever add the commentaries, yet references to brahmic text from nepal.

But as told, while knowing that even some parts of the suttapitaka in the tipitaka have to be chanced, it can not be expected to be perfect or to work out to be perfect before putting it into the shelf.

If particular names have to chanced late on, if the is no double naming on the pagename level, such can be made by steps online if the whole structur has certain consistence as a whole.5z

Things open to do at this point if wishing to do it in a larfe scale:

- proof and eventually correcting indexes and names of files
- renaming of files
- converting into wiki/wrap standard
- implementing anchors to the single suttas, chapters
- incl. Data table to each file (titel, url, date, origin...)
- upload into the folders (or incl folders) in the single lang-namespaces

So it's really open how one like to do it, but its not really a quick job to develop such, at least for my persons limits.
Posted by: Moritz
« on: July 13, 2018, 04:52:09 AM »

Sadhu. Thanks for the hints and explanations.

Quote
(on this place: anya filenames have no _any at the end and other files than the tipitaka-codes do not include the path in there name when it comes to tika and anya and simply new names. Maybe something that my person should change since it is difficuld to put them into the right folders without such a sort/search possibility in an explorer)

It seems some deeper nesting of indexes would be good. Some things are confusing.

For example, the index/TOC:
cs-rm:anya:niti-gantha-sangaho:index
contains this, which is also an index/TOC:
cs-rm:anya:niti-gantha-sangaho:caturarakkhadipani
within the same directory/namespace (cs-rm:anya:niti-gantha-sangaho ).
And from there there are links to actual texts, like cs-rm:anya:niti-gantha-sangaho:kayapaccavekkhana , also in the same diretory.
I think it would be good if for each TOC there would be another level/directory.

If including the path in the final page name as well then of course the final name could be very long with deep directories, like

cs-rm:anya:niti-gantha-sangaho:caturarakkhadipani:anya:niti-gantha-sangaho.caturarakkhadipani.kayapaccavekkhana_any , or even only the filename without namespace niti-gantha-sangaho:caturarakkhadipani:anya:niti-gantha-sangaho.caturarakkhadipani.kayapaccavekkhana_any could look very strange on the sitemap as well.

Or maybe just leave out such indermediary TOCs/indexes like cs-rm:anya:niti-gantha-sangaho:caturarakkhadipani which is already completely included in another bigger index file in the same directory.

So that there would be no "caturarakkhadipani" appearing in the final path, "caturarakkhadipani" being simply part of the one big "index".

Not sure if I understand this correctly:
Quote
Maybe something that my person should change since it is difficuld to put them into the right folders without such a sort/search possibility in an explorer
Why is it helpful to have the complete pathname also in the filename (separated with '.')? From my perspective it just produces very unnecessarily long filenames. But this is a problem with the tablet explorer software? (Don't really know what Bhante is using now.)

I could rename all files to not path-including filenames and simply put them in their "right" deeper directories if this seems helpful, (making a deep hieararchy everywhere, but with short filename in the end), but no time before next week.


(Not necessary to answer all in detail now. May Bhante find enough rest in between. I have no time to come back to this before next week.)

_/\_
Posted by: Johann
« on: July 13, 2018, 03:23:22 AM »

Nyom Moritz

All namespaces in latin scripts, yes, otherwise only troubles and the whole translation tools and lang-namespaces would be of no use at all.

The naming of folders and files now might be not perfect, such as double names, but such would be clear if starting to rename.

Other, ideologic renderings of single names can/could be made later by hand, step by step, online.

For your easy rendering, its possible good to put the files in the tree folder before, since it need to be made by hand and if not done with the root files it might be of more work, but probably the same for each lang. (on this place: anya filenames have no _any at the end and other files than the tipitaka-codes do not include the path in there name when it comes to tika and anya and simply new names. Maybe something that my person should change since it is difficuld to put them into the right folders without such a sort/search possibility in an explorer)
But if that things would not trouble to much, let it be like that for now. As Morits feels inspired to organice.
Posted by: Moritz
« on: July 12, 2018, 08:19:36 PM »

Vandami, Bhante _/\_

Sadhu! So just to make sure about plans to proceed:

As I understand, "readable" Latin script names/codes were used for the pages and namespaces, including also names from commentaries like: "cs-rm:anya:visuddhimagga:11._samadhiniddeso" whenever there are areas in the commentaries which do not correspond 1-to-1 to certain Tipitaka books/vaggas/pages.

If this structure is now clearly defined, it seems it would be good to use the same structure and pagenames/namespaces for all other scripts (Khmer, Thai, ...) as well.

So: Roman codes/pagenames for all scripts, in order to be able to use the language switch between different scripts.

I assume this like Bhante had in mind as well?

It could take some time (a week or more) till I can get to it, but if the names and structure of tables of content are all clearly defined in this way, I think I could import the tables of content with the same structure for all remaining scripts without much trouble.

(And for later at some point maybe: As mentioned before , might be possible to convert namespaces to use other scripts with .htaccess rules or some other tricks. Maybe even possible to switch between very different looking names with the langauge switch, with help of some JavaScript.)

_/\_
Posted by: Johann
« on: July 12, 2018, 11:44:54 AM »

Nyom Moritz,

Attached a list of the whole index cs-rm-namespace as my person thought it till here.

Tree structur is equal other lang-namespaces build.

It includes the names of the indexes, title, pagename, path, cscd-file name

Thought till here was to rename the xlm file into the listed pagenames, coverting them before according implementation_cscd in regard of wiki/html code (wrap) and anchors.

h1-Title might be good being the same like title

Than there have been strong considerations to make the structur total flat which would require to rename the "index" file in proper code pagenames, after of cause the same for all othe lang-namespaces, e.g. ati "index-files" would be good to get the same codes with "_ati" attached, single files as well "_{....}" (translator) attached.

No, on a dynamic page: does not makes sense and horror in maintaining indexes and name code systems. The ATI tree modified like now is fine. Maybe just looking for keeping the name index free for automatical folder indexes via a plugin. At least the sidemap is wonderful for quick finding and teaches/trains sati, flat is just by search engine good accessable.

So far the thought and state of progress. Atma thought to go on with the restyling of the tags and files from ati.

If thinking on different ways, it's just an idea of mine and there might be better, so don't feel limited by it.

(it might be that there are some double name conflicts in the indexlist for flat structur and renaming, and not checked if all files are matched. 1 or to are not listended, as the contained only the name of a group)
Posted by: Johann
« on: July 11, 2018, 07:10:17 PM »

Anya has been finished as well now.

The four great index should now have all files matched and each got a pagename.

It might be, that, since Tika and Anya is really not an ease, that there are double pagenames, so in this regard maybe a check if wishing to use it for a large addjusting.

Posted by: Johann
« on: July 09, 2018, 01:40:32 PM »

Sadhu

My person thinks that the/a sutta/vagga code as pagename is fine. Also raised a question in regard of multilingual here ()[ATI.eu] Multilingual - one "id" (namespace), diff. Names/Title languages/script . Name the "files in different languages/different does not make sense since there are directories/root-namespaces for each. The only

Chaper, book and actually title have no real consistence over all files. Might be that certain sections have and as knowing the files a little, subchaper, chaper ... are not so sure over all. Not to speak about the "chaotic", since many compilers, commentaries.

TOC-files just build the certain directory/folder, tree with its files on the last instance/level.

At the moment the new names look like this for a vagga for example:

mula: cs-rm:(path tipitaka:sut:an:)an01.v1{anchor #s001}
attha: cs-rm:(path tipitaka:sut:an:)an01.v1_att{anchor #s001}
tika: cs-rm:(path tipitaka:sut:an:)an01.v1_tik{anchor #s001}

Indexes have been modified, put together, such es Jataka 1,2,3 or reduced by one level, like for dn or mn.

if now adding title of file (most vagga), the search is quick and easie. As long english, since search engine and other features use primary pagenames.

My person came across a plugin for indexes for the sidebar which uses the first headline (h1) of each file. If all features adress in such or similar way, act on an alias from the file it self, all is fine, yet of course work.

Having the pagenames and structur as well as titel/alias well, all chategories/folders can fall aside of the lang-level and the root-levels, like tipitaka, atthakatha, library, author,ptf... (at the time it's also corresponding to each lang build, how ever, crosslinking is hard since requires to know sometimes a path of 3-4 levels). Having a flat structur makes all very easy.

Great to know that such fetching and renaming is possible. It might need another while till all is firm. Atma might ask some questions in progress of breeding handable, simple visions and might then try to transport it well for possible actions at large.
Posted by: Moritz
« on: July 09, 2018, 12:41:59 PM »

Vandami, Bhante _/\_

Is it "automatical" possibel to rename the xml files according a list Atma could provide xxx.xml -> =yy3.txt, xx2.xml -> = yy4.txt...

Yes.

Quote
And another question: Would it be possible to fetch a text under a certain tag, say "chapter" and rename files according their item under this tag?

On principle, that would be possible, yes. It seems even possible to use Khmer alphabet or other different than Roman in the name and URL: ២០._ផុស្សពុទ្ធវំសោ .
(I hope there are no hidden "dangers" of certain errors occurring when using non-western UTF-8 alphabets somewhere inside the Wiki titles.)

But maybe it would be easier to find the corresponding versions for each alphabet/script and switch between them when they are all named the same for each language?
Like it is possible at the moment with the language switch:

I think that is only possible if the files are all named in the same way for each language/script.

Maybe good if the base name for each file would be left as it is, corresponding to some code, like the XML files "e1208n.nrf0.xml" etc., but one could still add additional names, corresponding to book or chapter in the .htaccess rewrite rules .
Not sure if it is possible to set so many rules and if it could drastically reduce performance when having ten thousands of rules. ^-^


Quote
(problem the used titel is sometimes "chaper", and if not having seemingly "book" as well as multiuse, think just on mahavagga and other aspekts, but would be perfekt for wikiuse and search)

For each language, in the '/cscd' directory there are
2915 XML files
217 of them TOC/index files (ending in .toc.xml)

2651 occurrences of "chapter"
218 occurrences of "book"

So probably for each TOC there is one book.
(There is another "tipitaka.toc.xml" in the directory above "/cscd", probably corresponding to another "book" tag for the whole Tipitaka.)

Maybe this info is useful somehow. I could try to find out other numbers and structures later.

_/\_
Posted by: Johann
« on: July 09, 2018, 02:44:38 AM »

Nearly finished the tables.

Now just thinking about the possibilities, thinking also on making it most flat maybe.

Question, Nyom Moritz

Is it "automatical" possibel to rename the xml files according a list Atma could provide xxx.xml -> =yy3.txt, xx2.xml -> = yy4.txt...

And another question: Would it be possible to fetch a text under a certain tag, say "chapter" and rename files according their item under this tag? (problem the used titel is sometimes "chaper", and if not having seemingly "book" as well as multiuse, think just on mahavagga and other aspekts, but would be perfekt for wikiuse and search)

It's good to think well about the structur. All infos, name, book, file, url, origin, and credits ... would be good to carry in a/the datatable of each file.

What will be avaliabe maybe this evening ist a full list: "code" - "cscd-title" - "file-name" - (path) in addition to handle names and Datas of files.

Usual direct search is either by common code name or title. Maybe a combi or such as alias would be of cause nicer.

The whole need a lot of fine adjusting in addition, to find best also corresponding in attha, tika, anya... which Atma tried with codes as far as possible.
Havn't found a larger consistency over the files yet, and even the naming seems to have been changed in the way of progress, finding commentary-names under tipitaka and so on.
Posted by: Johann
« on: July 08, 2018, 09:27:29 AM »

Index Tikā as well. Anya might need some other 3-4h.
Posted by: Johann
« on: July 07, 2018, 02:40:43 AM »

Index Aṭṭhakathā und file-Benennung sollte nun auch passen.
Posted by: Johann
« on: July 04, 2018, 01:35:18 PM »

Verzeichnis(se) Tipitak (Mula) soweit fertig, und die Anleitung, Einarbeitungen des CS-Tipitaka , etwas aktualisiert.

(Wenn da etwas gemacht werden möchte. Sicher mit Verbesserungsauge und Gewiftheit auch gut verbesserbar.)
Posted by: Johann
« on: July 01, 2018, 09:00:58 AM »

Sadhu , Nyom Moritz .

cs-rm Struktur und Inhaltstabellen sollten im Großen so passen. Die Benennung hat Atma noch nicht fertig in den Verzeichnissen.

Atma denkt, da alles sehr komplex ist, ist es gut, wenn er rm soweit fertig macht und versucht einen Standard aufzuzeichnen.

Die Umwandlung der xml Texte wird im Wesentlichen gleich werden, wie zuvor in html, classen und divisionen und spans für WRAP passend. Herausforderung werden wie immer die Anker für die einzelnen Suttas sein.

Atma hatte vorgehabt die Verzeichnisse deshaln zuerst komplet zu machen.

Etwa so wie http://accesstoinsight.eu/doku.php?id=cs-rm:tipitaka:sut:mn:index
Unter jedem Vagga kommt dann noch Liste der einzelnen Sutta.

- Mūlapariyāyasuttaṃ [[:sut.mn.v1#sut.mn.001|sut.mn.001]]
- Sabbāsavasuttaṃ [[:sut.mn.v1#sut.mn.002|sut.mn.002]]
- ...

Code: nicht mehr so aktuell, siehe ati.eu Seite http://accesstoinsight.eu/doku.php?id=de:implementation_cscd - Einarbeitungen des CS-Tipitaka [Select]
< p rend="centre"> Namo tassa bhagavato arahato sammāsambuddhassa< /p>in

<div wrap_center>...</div>


< p rend="nikaya">... in

====== Name ======
<span wrap_suttaid #sut.mn>sut.mn</span>

< p rend="book">... in

====== Name ======
<span wrap_suttaid #sut.mn.p1>sut.mn.p1</span>

< p rend="chapter">... in

===== Name =====
<span wrap_suttaid #sut.mn.v1>sut.mn.v01</span>

< p rend="subhead">... in

==== Name ====
<span wrap_suttaid #[i]sut.mn.001[/i]>[b]sut.mn.001[/b]</span>

< p rend="bodytext" n="1"><hi rend="paranum">1</hi><hi rend="dot">.</hi>...< /p> in:

<span wrap_bodytext #s001><span wrap_para>[b]1.[/b]</span>...</span

Anker wie <pb ed="M" n="1.0001" /> in:

<span wrap_parasub #M_1.0001></span>

<note>...</note> in ((...)) um Fußnote zu bekommen.

< p rend="gatha1">...< /p> usw. in <span wrap_gatha1>...</span>

Am Ende Datatable

Name: ...
File-name: ...
Url: ...
Source: www. tipitaka.org/romn/cscd/s0201m.mul0.xml
...Date, Owner, Dedication


Im Großen könnte man sich an die Codierung aufgebaut im Khmer-Tipitaka halten, mit Korrekt div kleiner Fehler der Konsistenz, vaggas, subvaggas... was ja bis Dhp "fertg ist, Sinngemäß weiter.

Desto gewifter man es aufbaut, desto einfacher dann mit div. plugins und Kreuzreferenzen in alle sprachen und Ausgaben. Indexe automatisch aufbauen...

Wenn Nyom, was Struktur für leichtes händeln betrifft, etwas sieht, sich dessen annehmen möchte: freier Raum.

Handarbeit, denkt Atma, sind nach wie vor die Anker zu den einzelnen Suttas und das umbenennen der einzelnen xml files (das Atma ja schon fertig hatte, doch dann utf-16 entdeckte...).

Es ist gut, wenn die online-Version als Original gilt. Mit txt-file und regex direkt, dann ja sehr angenehm und multi-user-fähig und multi-tasking-fähig

Atma hatte alle files lokal umbenannt, wie "sut.mn.v01.txt"... "sut.an.01.v01.txt" usw. Atthakata, Anya, Tika, so gut wie möglich passend wo passen "sut.mn.v01_att.txt" (siehe Verzeichnisstruktur online)

Atma würde sich auf die bereits hochgeledenen Tables konzentrieren, und dort weiter machen, wie dn, mn. Aber flexible (an Arbeit ja freie Auswahl zu Genüge)

Atma hat eine Seite angelegt: Einarbeitungen des CS-Tipitaka , möchte dort alles geordnet anführen und dazu anregen.

Soweit mal im Groben und sicher nicht fehlerfrei ein "Grund-Pflichtenheft".


Posted by: Moritz
« on: July 01, 2018, 05:26:52 AM »

Thai und Kyrillisch sind nun auch hochgeladen und in die Download-Liste aufgenommen.

Ich könnte wohl auch alle Einzeldateien auf ATI hochladen, allerdings bin ich mir noch nicht über die beabsichtigte Struktur im Klaren.

Ich sehe, Sie haben zum Beispiel Namensräume cs:rm ("Chaṭṭha Saṅgāyana Roman"?) und pi:rm ("Pali Roman"?) angelegt und schon mit den XML-Dateien bevölkert.

Es sieht so aus, dass cs:rm die vollständige Variante ist. Soll diese Struktur so für alle Zeichensätze übernommen und beibehalten werden?

Falls ein paar Regex-Ersetzungen schon klar im Vorfeld parat, die vor dem Upload schon erledigt werden können, könnte ich das auch gleich tun.

_/\_