New Bilara launch date: Monday 17 August

[HongDa]

Thank you for your detailed feedback.

When a prompt such as “Pull request scheduled for 2 file(s)” appears, the relevant content is compared against the corresponding content in the published branch; a pull request is created if differences are found, but not if there are no differences.

To address this, I am considering adding a notification to inform the user which files ultimately resulted in a PR.

@sabbamitta

For publishing my own project at “sutta” level, it still created 5 pull requests. I believe that in my project, this could meanwhile all be done in one go, but for Bhante Sujato’s I don’t of course know. Apart from these two, there are no other projects with that many files. For Ajahn Brahmali’s vinaya project I also don’t know how many files have already been published after the Bilara transition.

Since the segment IDs across all files were previously aligned—affecting thousands of files—it is still possible for a single commit to involve more than 3,000 files. This exceeds GitHub’s limits and causes PR creation to fail; I anticipate addressing this issue after the transition period.

@sabbamitta

I am not sure how to understand the error message that “paths must belong to the same project”. Is each “name” file considered a separate project?

This restriction is in place to prevent one author from submitting another author’s content; I will check for this issue.

[sabbamitta]

@HongDa

a pull request is created if differences are found, but not if there are no differences

Well in cases where there are no changes I have seen a different notification. In that case it says “no modified files to publish in this location”.

But in the case described above there was at least one modified file, that is translation/de/site/name/sutta/an, which finally could be published, but only when I pressed “publish” for this one individual file.

translation/de/site/name/sutta/an is part of the folders translation/de/site/name/sutta, translation/de/site/name, and translation/de/site, but on none of these levels a publication was possible. The only possibility that worked was to publish the individual sutta.

This is only so for the “site” folder, apparently not for other folders. I suspect that site/name/sutta, site/name/vinaya, and site/name/abhidhamma do somehow count as different projects, but that’s just speculation, trying to find a possible cause. And it still wouldn’t explain why I can’t publish on translation/de/site/name/sutta level.

@HongDa

Since the segment IDs across all files were previously aligned—affecting thousands of files—it is still possible for a single commit to involve more than 3,000 files.

I believe that in my own project, all the segment ID changes have meanwhile been moved to “published”. A rough check shows that the last commit to almost all files in the “published” branch is not older than 2 months ago, and these oldest commits all have the commit message “align segment id 2”, with very few exceptions of files that probably didn’t have anything to align.

Once we publish for example the AN4 folder, all files with segment ID changes should have been published along with those with actual new edits. All folders of my project have now been published at least once.

But as I said, I don’t know about Bhante Sujato and Ajahn Brahmali. All other projects have far less files.

But anyway, this may still wait a while, it’s not a big problem. The “site” folder thing is more annoying.

[Hasantha]

Thank you so much @HongDa for answering all my questions and taking me step by step through the process for adding tags for my EBT thematic analysis project. I am happy to say I have managed to add the 15 starting tags and see how to edit them and add further ones as the work progresses.

I have managed to add the TAG-PLI-MS column to my Bilara page and can see these columns

1. The Pali
2. Bhante Sujato’s translation (as that is the one I will be using)
3. My remarks
4. The Tag colum (with a drop down menu with my 15 premade tags with the explanations)

I just dont see the save button (sorry to ask such a basic question at this stage!). When I added the first 10 tags and logged out they werent there when I came back.

@sujato
I will start with DN as suggested and I will make my own notes in the My remarks column for things to come back to and add the tags with my subjective view of the primary tag first and then any other tag that might be relevant as further tags (comma delineated). Pls let me know if that all sounds right and I will begin this weekend.

Also, Snowbird mentioned CIPS (Headwords sorted by number of locators) and Ven Pasanna pointed me to Leigh Brasington’s gradual training coding system and Ven NgXinZhao pointed me to an Obsidian vault, which already has tags! I forgot to discuss all these related bodies of work with you last night but assume I just plug ahead and we can work out how to intersect with these related bodies of work later? (PS: Those links are in the ‘Thematic Analysis of EBT’ thread but can send if you want?)

There are apparently 280k segments so I suspect this is going to take some time

Thanks again Hongda for your help and Bhante for letting me do this in Bilara, which seems like it is going to be so much easier than what I had planned originally!

[HongDa]

@Hasantha

I just dont see the save button (sorry to ask such a basic question at this stage!). When I added the first 10 tags and logged out they werent there when I came back.

Hi @Hasantha After selecting a tag, press the Enter key to save it automatically.

The appearance of this icon indicates that the save was successful.

Enter a comma after a tag to list other tags.

[Hasantha]

Oh I see, thanks. FYI when I used the drop down menu it doesnt automatically save

Thats not a problem, I can just type, but if you can activate the dropdown that will save me time pls

[Brahmali]

Hi @HongDa,

Good day from Oz!

There are a couple of things I have been hoping for a while would be implemented in the new bilara. I just wanted to check with you whether this is in the pipeline, or whether it has to be cleared with Bhante @Sujato first of all. The two things I have in mind are the following:

1. Editing of introductions, appendices, etc., using the bilara interface.
2. Allowing hyperlinks in bilara that connect to the same material.

This is not in any way meant to put pressure on you, but just to have a sense of what I can expect for the future.

Thank you!

[HongDa]

Ven. @Brahmali

Good day to you too!

I will be meeting with Bhante @sujato over the next couple of days and will discuss your requirement with him.

With Metta.

[ayyasoma]

Hello @HongDa,

Greetings from Italy!

I was wondering if it was in the plans to get the search bar back to how it was in the old Bilara… since nobody seems asking anything about it, I am starting to wonder if I was the only translator using that feature extensively.

I find it quite challenging to edit my translations with the new interface as I cannot easily check the renderings from my previous translations, nor can I easily update all of them once I decide to go with a new rendering. Because of this I am finding it easier to translate/edit on a Doc instead of using Bilara, as I can easily search in a doc … so I wanted to know if I should just switch everything to Docs and then just update Bilara once I’m ready to publish everything on Suttacentral, or if I should be patient and wait for the update.

Looking forward to hearing your thoughts!

All good wishes.

[HongDa]

@ayyasoma

I was wondering if it was in the plans to get the search bar back to how it was in the old Bilara… since nobody seems asking anything about it, I am starting to wonder if I was the only translator using that feature extensively.

Ven. @ayyasoma

Are you referring to this area?

[ayyasoma]

Yes, that’s the search bar I’m referring to.

[HongDa]

Hmm, since the old Bilara has been taken offline, I cannot make a direct comparison. Could you please describe the functionality you need? I will then schedule time to implement it.

[ayyasoma]

Thank you! Here are a few notes:

1. As you can see from example attached (“Tena kho” researched with old bilara and “Tena kho” researched in new bilara), in old bilara if I searched a Pāli word I would get *all* the related segments listed paired up with *my own* translations. With new Bilara I don’t get all my translations listed… nor some of them…. I just get a random stream of related Pāli segments, most of which haven’t been translated, and also a limited number of entries in which the word is present, but not all the entries available.
2. In old bilara I could search a particular word or sentence and enter another word/sentence in the “replacement” box: then, all my relevant translations would appear and if I wanted to change the rendering, I could just click on the “replace” button next to each entry (without having to type everything manually).
3. UID filter used to work properly: in new bilara it’s glitchy
4. Whenever I open new Bilara it lists by default Bhante Sujato’s translations: while I’m a big admirer of his work, I would prefer to search my translations… not his!

[sabbamitta]

@ayyasoma

1. in old bilara if I searched a Pāli word I would get *all* the related segments listed paired up with *my own* translations

Perhaps to add, in the old Bilara search it was possible to select which results you’d like to see. You could also see three languages together, like Pali, your own translation, plus Bhante Sujato’s, if you wanted to use this for reference.

@ayyasoma

2. In old bilara I could search a particular word or sentence and enter another word/sentence in the “replacement” box

But I do see a “replacement” box in the new Bilara?

I can’t say much about its functionality though because I am hardly ever using Bilara search.

[ayyasoma]

The replacement box is there, but it doesn’t work!

[HongDa]

Thanks @ayyasoma I will be making improvements to the search function in the near future.

And I tested the replace function, and it seems to be working correctly.

[Snowbird]

@ayyasoma

but it doesn’t work!

For the purpose of troubleshooting, it’s always best if you can go step by step with exactly what you are trying to do and what the results are vs. what they are expected to be. The more details the easier it will be to fix (with fewer back-and-forths)

[ayyasoma]

Thank you Hongda.

Re: the replacement tab, there is no ‘submit button’ on my version of Bilara.

Please see screenshot attached.

[sabbamitta]

I just encountered a very old comment (not meant for publishing) in a title segment. I’m trying to delete it, but this is not possible. What should I do?

I tried to delete it by creating a pull request in the repository, but it seems not to be present there:

The comment is in AN4.112, but this is not found in the list here.

So should I just consider this comment as “non-existent” and leave it where it is?

[HongDa]

@ayyasoma

Re: the replacement tab, there is no ‘submit button’ on my version of Bilara.

Hi @ayyasoma

I checked and found that the replace function was previously restricted to superusers; I have made changes so that authors can now use this function for their own translations.

need to perform a hard refresh of Bilara in browser.

• Windows / Linux：Ctrl + F5 Or Ctrl + Shift + R

• macOS：Command + Shift + R

Next, I will make improvements to the UID filter functionality.