No, it was caused by my fix in 4.0u1. The fix was functional, but left paths un-normalized (potentially containing ../). This is now also addressed in trunk (4.0u2).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please provide a screenshot.
This is a side effect of recent fixes to path resolution. It appears to be merely a cosmetic issue; paths are still resolved correctly.
This is fixed in trunk.
Was it fixed in 4.0 update 1?
Didier
I have my answer (it was not). I was asking because the fix was not yet available when doing svn update (it is now).
Didier
No, it was caused by my fix in 4.0u1. The fix was functional, but left paths un-normalized (potentially containing
../
). This is now also addressed in trunk (4.0u2).Fixed in the released version 4.0.1 of OmegaT.
Didier