The arrangement of blurbs in SN is slightly different than how it’s done in the old cat. In the old cat, the introduction to a collection is grouped together with the suttas in that collection, so it is easier for me to translate the related suttas and intro in the same place. Example, if I want to translate the blurbs sequentially for sn18 (intro to a collection) and then sn18.1 (individual sutta) in the new cat, I have to do a lot of scrolling to get to these 2 blurbs.
The loading is significantly slower.
I can’t see the vertical scrollbar in the new cat. If the list is long, it is hard to scroll quickly without vertical scrollbar.
The search panel on the right goes out of view as soon as I scroll down. Shouldn’t it be sticky?
I can edit my translations now. Thanks! Am I supposed to be able to edit the root segments? I can see that that would be a sensitive permission to give out. If I am, that isn’t working yet. If not, then things seem to be in order now.
Question: When I click the merge button on a root segment, I get this display:
Regarding this, our main efforts have been in making sure the split/merge actually works well. In terms of usage what we have now is just a suggestion. I suspect it’ll get clunky if it’s needed a lot. For myself, I’ll just use it for an occasional correction. But for you it might be used a lot more. Anyway, let’s get past the first hurdle of making sure it actually works, then consider optimizing the UI if need be.
I agree that hopefully this won’t be a feature we use much. The UI does need to function, though, for me to check if it works.
This morning, I checked how it works in multiple browsers and noticed that Chrome is displaying both the “Cancel Merge” and “Check Merge, Then Confirm” button, but Edge and Firefox are still only displaying “Cancel Merge”. I usually use Edge or Firefox, so this may have been the reason I couldn’t see the Confirm button.
Also, I can see that the HTML is going to be <p>{} {}</p>. A pop-up window advises me to make sure it’s correct, but I’m not able to edit it in any of the three browsers. Should it be <p>{}</p> instead of <p>{} {}</p>?
When I test the “Confirm” button in Chrome I get this pop-up (which looks good!):
Okay, that worked. I was able to publish the new translation file for the merged segments.
Now, I decided to check the split segments feature to reverse the merges. But … this doesn’t look functional for me because I’m not able to cut and paste the Chinese into the new empty segment. Or is there another process to follow for splitting the segments? Here is a screenshot from Chrome:
Okay. I tried to do the split operation this morning. It seemed to be working okay on my end. I found the toggle to turn on the merge and split buttons. And I do indeed have the ability to edit the root and html segments now.
When I attempted the first split, however, there was an error message that appeared for a few seconds in red. It last just long enough for me to scan it and see that there was some technical info in it like a stack trace or something, but then it disappeared. Subsequent attempts to split the segments that I had merged brought up this message:
It seems that I need to do something to attempt the split again, but there’s no obvious way to do that that I can see.
Another thing I realized, too, is that I believe the new segment ea19.1:1.2 really should be the first segment of the next paragraph, meaning that I will need to change it to ea19.1:2.1 and have the subsequent segments renumber themselves. Is there a way to do that currently?
But that’s as far as I could go with the test because I’m not sure how to save the first split that I attempted. Something that might have caused the error is that I didn’t bring up my translation and move the English into the new segment before I hit “confirm split” … perhaps the empty segment caused an exception to be thrown?
If you can’t override the default OK and Cancel to yes and no then don’t ask a yes or no question. The text in the dialogue needs to be rewritten to say
Click OK to discard and start a new split.
I’m all for using browser APIs. But I hate these dialogues where the choices given don’t match the text. It’s not impossible for a native speaker to guess what they should click. But there should be zero doubt.
Not sure if this problem is persisting, but there rule is there must be one and only one {} in each segment. If you see <p>{} {}</p> again, it’s an error.
It looks to me like the code that generates the new html is a concatentation of the html for the two segments being merged. It might be good to check for {} {} after the concatenation and then replace it with {} in the code. Then there won’t be an opportunity for a human to overlook it.
I have discussed this with Hongda, he’s aware of the requirements. I’m not sure if he had time to implement this before he went on holiday. Never mind, he’s back next week.
