Greetings to all, especially those using Bilara for translations. We’ve developed the new Bilara to a point where I think it’s feature-complete. We’d like to invite people to come on board and test it out and see what feedback you might have.
Please let us know in the comments here if you’d be interested.
There’s no particular requirements for testers, just try it out, do whatever you feel like and let us know.
While we’re here, I’ll take the chance to talk about the roadmap for the new Bilara.
Once we’re happy with it, the new step is to refresh the data. Currently we’re using an old data set from when we started development. It’s at that point that things get tricky, because we don’t want to get into merging data from multiple sources. That adds another layer of complexity, so I think it’s better to have a clean change. So that means:
So there will be a time when no-one can work on their translations. I anticipate that this will be only a short time, hopefully less than a day. But, well, you know how these things go.
Anyway, that’s the step after next. I just want to make sure there’s no surprises. We’ll flag these upcoming changes on the old Bilara when we have some dates in mind.
Of course I am interested! Thank you so much to you and @HongDa and everybody else involved for tirelessly working on this! Looking forward to trying it out later today.
We can actually notify all translators as a group @Translators . I hope they have all been added. But probably the latest projects won’t be found in the new Bilara yet, as this has old data only.
Actually, I just logged in, and it looks a bit … pale? The theme selection has also disappeared:
Just to clarify, can we still work on our translations in old Bilara right now? You said this plan is “the step after next” and I was just going to ammend some translations, so better to know when and when not to do that.
As I understand it, we have to do our actual work on the old Bilara at the moment. The new one is only for testing, using old data, and any changes we make there will not be included in our projects.
Another thing I noticed, trying to commit a change:
I don’t see a green check mark, or any hint whatsoever that something has been committed.
Instead of taking the text that I typed in the segment field it took the text of the first TM suggestion that was shown on this segment—but this wasn’t what I tried to type.
Or actually, even if I don’t type anything after having clicked into a segment and just hit “enter” (because I want to move to the next segment without making a change), it still replaces the original text of the segment by the text of the first TM suggestion. (Note: Just in order to read what the following segment is, I need to move my focus further down because otherwise this segment, and a few more, is overlaid by the TM suggestions; but apparently this is not possible without introducing unwanted changes in my current segment.)
Ah, great! So this is much better for viewing the TM suggestions. But still the behavior is as described above (see points 1 to 3 of my previous comment).
Also, after committing a change it is not possible to revert it by using CTRL + Z. If I type that, just nothing happens.
@HongDa, although I am posting a few things that cause difficulties here, I don’t want to sound just negative. Overall, the new Bilara looks very clean and nice, and the choice of themes is truly impressive! I hope you know that I always appreciate your work A LOT! Whenever there is a problem you are always very quick to help out and fix it, often in amazing ways. Let me just take the opportunity and express my huge gratitude here!
Don’t ask me why, but now this seems to work as expected!
I have to modify this a bit:
I can make edits and see green tick marks. I also can edit in my segment and commit what I typed. But it still happens that I get unwanted changes when just trying to click through several segments, not wanting to change anything.
I just tried to publish a file with a change—not sure where that pull request is going, but there must be one somewhere now.
Thank you also for the diff viewer, this seems to be a very useful thing to have!