2016-11-30 12:36 GMT+03:00 Samuli Seppänen <sam...@openvpn.net>: > Il 30/11/2016 09:53, Илья Шипицин ha scritto: > >> Hello, >> >> as we finished x86 + x64 installer, we can do something else now. >> @mattock, which installer are you going to build ? >> >> it used to be (ndis5, ndis6) x (x86, x64) matrix, what will be future >> matrix ? >> > > As discussed earlier bloating the (2.4) installers with NDIS5 drivers is > not worth it. NDIS5 driver is only aimed for Windows XP, and we have > dropped XP support in OpenVPN 2.4 already. Also, OpenvPN 2.3 will see fewer > and fewer fixes as 2.4.x releases stabilize. Eventually 2.3 will go into > "high severity security fixes only"-mode, like 2.2 did several years ago. > > So let's not beat the dead horse (NDIS5) anymore :). > > >> (and, yes, I'm going to build multi-language installer, probably right >> after 2.4 release) >> > > This makes sense. Any plans on how you're going to do it? >
as we do not support windows 2000 anymore, we can easily switch to unicode. there are few questions 1) unicode nsis under linux (we use windows+mingw+nsis unicode, so, I'm not sure about linux) 2) split installer into several language files (as done for openvpn-gui) 3) test everything it is not difficult, but it is time consuming, I'm afraid we will test it properly before 2.4 > > Another internationalization aspect we could improve is how we store > translations for OpenVPN-GUI. Editing the resource files directly is clumsy > and error-prone, as the files contain lots of "stuff" that is not meant to > be translated. A simple key-value file would be much easier, although in > OpenVPN-GUI's case the hardcoded window sizes make this more complex. > it makes sense to convert openvpn-gui resources into visual studio format. @selvanair some times ago told something like that. as for the rest, separate resources are just fine. > > Also I'm not sure how easy it would be to separate the translatable > strings into a separate file. I would guess that the actual .res files > could be generated on the fly from a template and the key-value file by the > build scripts. > > it looks overcomplicated. some kind of "post build operation" which will identifies missing language resources would be nice however > -- > Samuli Seppänen > Community Manager > OpenVPN Technologies, Inc > > irc freenode net: mattock >
------------------------------------------------------------------------------
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
