Giving te fact that version 0.8.6d is THE official version currently offered on download, perhaps it might be a good idea to distribute a bug-free version ...F**k, F**k, I will do another version if you want.
Because this is more difficult to do.Giving te fact that version 0.8.6d is THE official version currently offered on download, perhaps it might be a good idea to distribute a bug-free version ...F**k, F**k, I will do another version if you want.
(why the other time this same problem was quickly fixed, but this time appears to be ignored ? why the problem reappeared once it was fixed ? why version 0.9.0 is clean from this point of view ?)
Cristi
I find strange this particular situation, in which this same bug was once identified and somehow solved, and now it is back again without much chances for solving.please don't blame us too much for wxwidgets bugs.
I tested the Windows precompiled d version approx since its beginning (this was after some time the c version was official) and since then a few times again (from time to time I do the same with version 0.9.x). For the d (beta) version this bug was always there live and well, but being a beta I put no particular attention to this, even if I asked myself why the bug was back again shortly after it was already fixed in version c.You didn't test windows compilation before we release the binary, did you ?
It was identified and forgotten, and guess what, it is a wxwidgets bug, THEIR configure script doesn't recognize --enable-unicode. Hopefully there will be another build for windows in some time.I find strange this particular situation, in which this same bug was once identified and somehow solved, and now it is back again without much chances for solving.please don't blame us too much for wxwidgets bugs.
I don't know why it has not been included, there is absolutely no reason except the person who merge translations (xtophe) forgotten about it, that can happen. Please resend your translation.[offtopic] Other than this, I don't understand why the updated Romanian translation was not included in the final package, giving the fact that I have sent a language file update on 14 November (i.e. before official 0.8.6d release) specifically for version 0.8.x (and then again on 9 December, whereas this latest update appears to be missing from the trunk – perhaps because it is a 0.8.x version instead of a true 0.9.x version ?).
I am waiting for a stable release for version 0.9.x (to be frozen, or something), so I can switch my Romanian translation to this version (where will be published this kind of information ?). Until then I am offering full language support for version 0.8.x. [/offtopic]
Next time don't think we notice all the bugsI tested the Windows precompiled d version approx since its beginning (this was after some time the c version was official) and since then a few times again (from time to time I do the same with version 0.9.x). For the d (beta) version this bug was always there live and well, but being a beta I put no particular attention to this, even if I asked myself why the bug was back again shortly after it was already fixed in version c.You didn't test windows compilation before we release the binary, did you ?
No need for true resending, the package is available at anytime at this location (last update was on 9 December if I remember well). The file is actively maintained and is associated with my page here (page is in Romanian language only).I don't know why it has not been included, there is absolutely no reason except the person who merge translations (xtophe) forgotten about it, that can happen. Please resend your translation.
Return to “VLC media player for Windows Troubleshooting”
Users browsing this forum: Bing [Bot] and 23 guests