Ok, sounds good. I just started on mn-guide-sujato but I will let you know when I start on the names. Thank you for the suggestion and for the details on this.
1 Like
Great! That will benefit many people, not just the French. I think these indexes are really useful tools—if they work.
1 Like
In the 19th Saṁyutta, only the first Sutta has a blurb. Can the others be added please? Bhante @sujato 
1 Like
Thanks for the prompt Ayya, this is done
1 Like
Okay, I need a new post again. This job is longer than D&D allows. 
- swift pair of messengers: SN 35.204 → SN35.245 on SC
- sword drawn from its scabbard: DN 11, 12 → DN 10 on SC
- tall building in central square: DN 11, 12 → DN 10 on SC; MN 39 is mentioned in the list, but has a different simile for the same point on SC, both in translation and in root, so I remove it
- tendon in fire: SN 7.46 → SN 7.49 on SC
- tortoise evading a jackal: SN 35.199 → SN 35.240 on SC
- travel, from village to village: DN 11, 12 → DN 10 on SC
- travel, in desolate country: DN 11, 12 → DN 10 on SC
- treasure, doorways leading to: AN 11.17 → AN 11.16 on SC
- tree, gold: Thig 14 → Thig 14.1 on SC
- turban or head on fire, person with: wrong link format,
href='/an06.20'→href='/an6.20' - uprighting what had been overturned: The following Suttas don’t have the simile on SC (due to abbreviation) and should be removed from the list: MN 57, MN 58, MN 72, SN 7.2, SN 7.6, SN 7.14, SN 7.17, SN 12.48, SN 42.3, SN 42.6, SN 42.8, SN 42.9, AN 3.65, AN 4.111, AN 4.184, AN 10.176, AN 10.177 (so it seems AtI has expanded the root text in a lot of cases, or has a different root text)
- village, empty: SN 35.197 → SN 35.238 on SC
- vipers: SN 35.197 → SN 35.238 on SC
- water, drops in a hot pan: SN 35.203 → SN 35.244 on SC
- wounded man wandering in jungle: SN 35.206 → SN 35.247 on SC
- wounds, dressing: AN 11.18 → AN 11.17 on SC
- yokes, sense bases and their objects: SN 35.191 → SN 35.232 on SC
Hey all, just a general polite request.
Try not to publish too often. We’ve got a bunch of French translations, great to see! But better not publish each sutta individually.
Basically, whenever anything is published or updated, it goes through a manual process that has to be approved, either by Carmi or I, and each run requires maybe 5 minutes of computer crunching time. There are boring technical reasons why this is so, but the outcome is that it’s better to process things by batch.
As a normal standard, I’d suggest that if you’re working regularly, publish a batch no more than once a week. Maybe publish per vagga rather than per sutta.
It’s okay to publish or update an individual sutta now and then, but try not to make it your normal workflow.
For myself, I translated the four nikayas before publishing any of them, and I really value that. So many times, I thought I had it, then went back and changed it because of something that I came across much later.
Take your time, do the best quality work you possibly can, and remember the simile of the chariot!
7 Likes
Thanks, I will keep this in mind and apologies for the trouble in the past few months. 
2 Likes
No apologies needed, love and respect only!
5 Likes
Dear all,
As you are already aware of, we have a few unsafe pages for our translation work. That means, these pages have different sorts of problems that might cause a new revision to be required after translating them. Unless you have a good reason, you don’t need to waste time with them until they are fixed.
As a first step to make the “index of similes” a safe page, I have now done the German translation and along the way found and fixed lots of misleading links. I have now finished this work, and here you can find all the fixes that I have noted. They are fixed in the German version, but still need to be done in the English and all other versions.
My list only includes wrong links, not any problems with content. There are in some cases passages that are interpreted differently on Access to Insight (where the index originally stems from) and in the segmented translations on SC, so a user might not find a simile even if the link points them to the correct Sutta. In the German version of the index, I have adapted such things, as well as differences in terminology, so that a user can find things that are actually there on SC. But such things are not part of my list, as each translator might choose different paths for their translation.
The link issues I found are all listed in these several posts (D&D only allows further editing one post for a certain time, so I had to start new posts a few times):
- Discussion for Bilara users - #78 by sabbamitta
- Discussion for Bilara users - #81 by sabbamitta
- Discussion for Bilara users - #95 by sabbamitta
- Discussion for Bilara users - #114 by sabbamitta
You can all use these to make the respective fixes in your own language files.
However, this does not yet make the simile index a safe file to translate. There is still the small problem with the alphabet. In the names index, this affects only a few entries, but in the simile index, it’s just everywhere!
But to fix this, we need a developer.
3 Likes
I just had a brainwave and propose a new approach to fixing this. The basic idea is that a translator who wishes can export the relevant page as plain HTML, edit the HTML as they like, they use that instead of the Bilara file.
3 Likes
Wow, sounds good, but I have a few questions.
How do I do this?
How will that work on the website?
- Will it still be the case that, when a user has set their language to “x”, the file, say, the simile index, is automatically shown in language x, whether this is a Bilara file or not?
- And when, language set to “x”, they type
?lang=yin their URL line, will that work as well, no matter whether any of these languages has their file in Bilara or not?
Hello all, is it just me or Bilara isn’t loading data right now? I tried hard refresh several times with no success.
1 Like
You’re right, it looks bad. Going to alert Blake …
1 Like
Oups hope not too bad.
Thanks a lot.
1 Like
“Looks bad” means it’s down on my end too. Usually it is enough to reboot the server, which only Blake can do.
1 Like
Ah ok good 
1 Like
Try reloading your page, it should be back now.
1 Like
Yes it is. Thanks a lot again for your help
1 Like