tag:blogger.com,1999:blog-7523589.post1152453396177727213..comments2024-02-20T19:17:55.835+01:00Comments on TSDgeos' blog: Qt Designer texts: disambiguation vs commentAlbert Astals Cidhttp://www.blogger.com/profile/12001470108926138921noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7523589.post-17408451376352429352013-04-19T20:15:24.335+02:002013-04-19T20:15:24.335+02:00Sorry: for "translator behaviour" i mean...Sorry: for "translator behaviour" i meant "developer behaviour", obviously...Orestes Mashttps://www.blogger.com/profile/03770384234633828925noreply@blogger.comtag:blogger.com,1999:blog-7523589.post-49851077008811721402013-04-19T20:13:26.874+02:002013-04-19T20:13:26.874+02:00Interesting. Let me say that this translator behav...Interesting. Let me say that this translator behaviour may be induced by two things:<br /><br />1) The somewhat confusing labelling of "disambiguation" and "comment" fields in Qt Designer.<br /><br />2) How this disambiguation fields appear in lokalize (under "unit metadata" window): Designer's disambiguation field appears under a boldface "Context:" label in lokalize, while Designer's comment field doesn't appear under any heading in lokalize. Worst, it appears under an unrelated "Add a comment..." link, which is confusing, and also the comment field is merged with other (auto-generated) context in the same line.<br /><br />Hope some day lokalize's developers will fix it.Orestes Mashttps://www.blogger.com/profile/03770384234633828925noreply@blogger.com