Direct links to segments not working for DĀ and EĀ

Feedback
1

Links to segmented text work for MĀ and SĀ
https://suttacentral.net/ma1/en/patton#ma1:1.2
https://suttacentral.net/sa1/en/patton#sa1:1.2

but not for DĀ and EĀ

https://suttacentral.net/da1/en/patton#da1:1.2
https://suttacentral.net/ea1.1/en/patton#ea1.1:1.2

1 Like
2

Looks like the broken ones are legacy texts. The ids will be different. Notice the sc part of the id.

3

Hm, I believe these are all translations by @cdpatton using Bilara?

Ooops, you’re right, I haven’t noticed the legacy tag on the suttaplex card.

No segment IDs then for DĀ and EĀ :sob:.

4

Yeah, when troubleshooting any SC problem the first step is not “turn it off and back on,” it’s “is this a Bilara/legacy text issue?”

I don’t think that the root text for the EA is even in the Bilara system yet. But cdpatton would know better than I.

1 Like
5

No, there are only a few of my translations in Bilara. At some point, I will be addressing this. I’m segmenting the Chinese on my end, just need to generate the data in a format someone can insert into Bilara for me. Any volunteers?

1 Like
6

What format is your segmented data in?

1 Like
7

I see. I only checked the first few translations from each collection and assumed there were more. Since there are so few segmented translations I will disable the segmented link notation for agmas for the time being (automatic linking to all suttas from the main agama collections will still work).

Unfortunately I know absolutely nothing about the inner workings of Bilara, so I’ll be of no use here, hope someone who’s knowledgeable enough will volunteer.

2 Likes
8

Currently, it’s in a local database, which I can output into whatever text format is needed with a script. We had sort of kicked around the idea of using an ad hoc html format that yet another script could convert to whatever format Bilara I/O uses to go back and forth with Bilara’s data set. But, I could transform the data into whatever format is needed. I’m on Win11 at home and I’ve had little luck with running Bilara I/O myself.

1 Like
9

If you can output a csv file, then literally all you need to do is a regex in a text editor to change it into json. I guess the issue is dealing with multiple files. In that case then bilara i/o might be the solution.

I have no idea about adding new root texts into Bilara, but if you are the authority on setting the segment numbers, then going from csv to json is extremely easy. Feel free to DM me if you need my help. Or if you prefer we can chat here or a new thread.

2 Likes