Hello
How can I add Bhante Sujato’s english translation to my workspace in Bilara?
I had it set up that way previously but recently my browser settings changed and the workspace got reset, now I can’t find it in the list when I press the pink button in the top right corner.
For some reason I can’t scroll up and down the list:
Yes, and that’s a big bug. It won’t be fixed in the existing Bilara version, and hopefully () the new version won’t have it.
What you can do is make the font size in your browser small enough so that you can see the entire list. Then perhaps with the help of a magnifying glass you might find the column you wish to add.
Sorry that I can’t point to a more elegant solution!
Spanish version of the Vedanā Saṃyutta finished, and reviewed by a Pali scholar. I’ve made the pull request. This translation was funded by the Hemera Foundation for the Insight Meditation Center (Redwood City, Gil Fronsdal’s place) and I’m asking them whether they want to be mentioned, but I don’t know if SC has any policy regarding this.
There’s no rush, just did the pull request to publish so.
I have two other questions I hope to get some help with.
How to export a translation, e.g. only target language? I found a thread that seems to discuss this but I’m way behind the nerdiness required for that. The IMC will publish the translation on their website too.
Similarly, to import a translation. I ask because, Spanish and Catalan being so close, I could very easily produce a Catalan version of SN 36 from the Spanish, upload it and then check it against the Pali.
Hopefully these things will already be explained in a thread I can simply be pointed to, and I don’t take much of anyone’s time. Thanks!
Hmm … I am also not very nerdy, and this is what I do to keep a local backup of my translations on my machine: I copy the individual sutta files from my folder in the repository and save it. Your folder (unpublished version) is here (you can’t see the published version yet until your pull request has been merged).
But not sure if this is what you are after.
It’s fairly easy to do this in Bilara, no need to import afterwards because it’s right there. You go to your Catalan project and open a new column with your Spanish translation, then you copy the segments from Spanish to Catalan and edit what is necessary. Would that work?
Otherwise it’s also possible to import a ready-made .jason document into the repository, but I don’t think producing this would be easier than doing it right there in Bilara.
It would, and I could do it this way, but I was looking for a lazier option. Spanish and Catalan are such close languages that a google/gpt translation is very reliable. Once that is put side by side the Pali, I would go through it and make any necessary changes.
I can copy-paste each sutta’s .json file (or use AI for bulkier ways to do that), translate it automatically, then put that on bilara and ammend as usual. I’ve just tried except the last step, because after creating a new file in my Catalan SN 36 folder, I wasn’t sure about “Commit changes” and pull requests and the like, so I aborted. But that’d be an easy way actually.
Thanks @Snowbird, but I think that for the simple purpose of exporting the Spanish it won’t be necessary. They can copy it from SC once published, or use the readingfaithfully preview—which is how I showed them my translation.
A note: I’m just feeling a warm glow in my body, such appreciation for the wonderfulness of this community of people helping each other do something as worthwhile as translating these early Buddhist voices
I am very sorry to say, but this “lazier option” is not for SuttaCentral. It is Bhante Sujato’s explicit wish that translators don’t use any AI tools for translations to be published on this site, and SuttaCentral even uses being free of AI as distinguishing feature (see note on footer).
I would not just paste an AI translation, of course. In any case, if this is the rule, I’ll follow it When I have time to do it “manually”, I will. Cheers!
Your post is 6 hours back, and I just tried out Bilara right now. For me it works totally as expected. Maybe try again now. Maybe hard refresh your page first. (Could it be that you are logged out from github accidentally? Just speculating …)