2

Thoughts on the New editor

Michal Kumor Rpd

December 06, 2018 08:57

None

Follow

 

Hello, 

I have been using the new editor for two or three months already and I would like to share some of my thoughts/questions/suggestions/ideas that popped up in my mind in the meantime. 

1. Why is it not possible to merge segments at will? Documents in our company have many sentences chopped off in the middle and it infuriates me that I cannot merge them only because they were not split previously. Could you guys please make it possible? 
2. We use codyt mode and I am wondering, why I cannot see who undertook the translation of the document? What we do now is leave a comment when accepting a job, because otherwise it would be impossible to know which of my colleages is translating the document! Or maybe I'm just not smart enough to check it the "proper" way? 
3. How to access comments to the job after opening it in the new editor? I can leave comments easily but how can I see them? I know how to do that from the job list or from the old editor, but how to do this from new editor? If it's not possible - why? If it's possible - why is it so counter-intuitive that I cannot find it after 2 months of using the new editor?
4. I have set my editor to show 100 segments at once. My logic tells me it should show segments no. 1 to 100 on the first page, 101 to 200 on the second etc. The new editor, however, shows 100 segments, but it thinks that a split segment is two segments – so for example, in one of my documents page 6 shows segments no 477 to 575.
5. The undo combo “CTRL+Z” behaviour is funky. When I try to undo some changes in a segment, it sometimes undoes a whole sentence, sometimes a word or two, sometimes it even pastes some random sentence from another segment inside the one I try to undo. Also, when I try to undo when creating a comment, it undoes changes in the last segment I have been working on – not in the comment itself. CTRL-Z feels like a really basic function, so I hope it can be resolved quickly.
6. Adding new repository entries is a pain right now. The window for adding new entry covers the whole editor screen and it cannot be minimized, so if I want to add a new entry, I have to copy source or target language phrase, paste it, and then write the translation/source expression from memory. I already wrote about it before, but haven’t seen any improvements. What I hope for is: smaller window for adding new repositories (right now the window has loads of unnecessary whitespace), ability to minimize the window and move it around. I have marked some of the wasted space in the screenshot below.

Also – when I add a repository from within a job, why the language I am translating is set as “Translation” and the one I am translating to is “Source”? See below: when I translate from Chinese to Polish, why is Chinese marked as “Translation(s)” and Polish as “Source”?

 

These are only the complaints that I remember off the top of my head, and from my perspective these are very basic things that should work with no issues.

Best regards,

Michal

 

 

• Facebook
• Twitter
• LinkedIn

5 comments

• 
  Alexandre Ronin December 14, 2018 10:17 Official comment

  Hello Michal,

   

  Thank you very much for your valuable feedback. Please allow me to address your issues one by one.

  1. Indeed, merging segments is only possible for segments that were previously split. This is not specific to the new editor, as it was never possible, even in the old version. Implementing this currently would be a challenge, but I encourage you to submit this as a feature suggestion in the dedicated forum so that other users can also vote and give their opinion, which helps us determine what we should prioritize.

  2. and 3. Seeing comments on the job, or the workflow steps is currently not possible, and is something we're planning to add when we work on the new interfaces for Wordbee, as these are not specific to the editor. We have projects in our pipeline that will address these points in the future.

  4. Indeed, when displaying sub-segments, each sub-segment is considered a segment for display. This was also the case in the old editor. While I can conceive why this may seem like a problem, it isn't for performance reasons. Please allow me to explain. In some cases, your document can be segmented in a way that each segment has sub-segments. For example, if each segment has 5 sub-segments and you choose to display 100 segments per page, you'll have 500 segments displayed on your page, and this will cause severe performance problems, if not a complete crash of your browser window as the browser can't keep up with showing that many segments. This is something we need to keep in place to make sure these things don't happen. This is also a reason why we don't recommend showing too many segments if your computer can't keep up as this affects performance.

  5. The Ctrl+Z function is "event" based, meaning that everytime you hit the spacebar, insert an autocomplete suggestion, add a term from the translation finder, or anything, it should add an event which the segment will roll back to when hitting Ctrl + Z, which could explain why sometimes, whole chunks of text are removed. These events only concern text changes in the segment, meaning that Ctrl + Z cannot remove comments as they're completely separated. However, if you have an example of something that you think is an issue, I encourage you to submit a support ticket with a video recording to show us exactly what's going on as we're not observing any particular issues with the Undo function at the moment.

  6. These suggestions are duly noted. The segment editor which is also used when adding new segments to resources is currently being rewritten, and these will take into account your remarks. I don't have a specific ETA for this, but we expect this to be ready before next Spring

   

  I hope that these answers will suit you. Please let us know if you have any further concerns.

  Kind regards,

  Alex

• 0
  
  Michal Kumor Rpd December 14, 2018 10:34

  Dear Alex, 

  Thank you for your in-depth reply! 

  Regarding 5: I cannot really make a video of the bug I sometimes encounter, becuase it is really unpredictable, but what happens is: 

  editing segment A -> then editing segment B -> trying to undo text in segment B by using CTRL+Z -> whole of segment A or a part of it is copied inside the segment B

  and regarding comments: 

  editing segment A -> adding a new comment -> trying to undo text in the comment (when it is still being edited) with CTRL+Z -> the content of segment A is being undone.

  It was also brought to my attention that CTRL+Z is by default used as a shortcut for "move back to previous text". I find that a little confusing to use such a common combination for a shortcut and I cannot find a way to disable the shortcut/erase the combination from it. All I could do is replace the combination with something else. 

  Eagerly waiting for the improvements you have mentioned, especially for the segment editor.

  Best regards,

  Michal

• 0
  
  Alexandre Ronin December 14, 2018 10:51

  Hello Michal,

   

  Thank you for your reply with some details about point 5.

  Regarding your first point, I recall we fixed an issue not too long ago where shortcuts could sometimes trigger on previous segments. Do you recall this happening recently? If yes, would you have an approximate date so that I can cross-check with the fix release date?

  And regarding your second point, I appreciate the explanation and now understand what you were talking about. I have reproduced the problem and we'll be working on a fix for this.

  Finally, about your last point, we've decided to replace Ctrl+Z by default as we observed some very strange behavior when using the default shortcut's function. This allowed us to have finer control over it's behavior when inserting hits from the translation finder for example and it's something we're not planning on changing. If this behavior is not your desired behavior, then you can change the shortcut as you've already found.

   

  Closing note, you're not the only person requesting improvements to the segment editor, but your comments prompts us to get this ready even faster. Thanks once more for your feedback.

   

  Kind regards,

  Alex

• 0
  
  Michal Kumor Rpd December 14, 2018 11:16

  Regarding your first point, I recall we fixed an issue not too long ago where shortcuts could sometimes trigger on previous segments. Do you recall this happening recently? If yes, would you have an approximate date so that I can cross-check with the fix release date?

  It actually happened to me just yesterday. 

  Thank you for your support!

   

• 0
  
  Alexandre Ronin December 14, 2018 14:57

  Hi Michal,

  Thanks for confirming. We'll look into it and try to find a pattern to reproduce this issue. If you have any new information about this, please do not hesitate to submit a support ticket with more details to help us get this resolved faster.

  Have a nice afternoon.

  Alex