30/05/2014 21:33, sgrìobh Marcin GTriderXC.tk:> You don't need any virtual machine to test different desktop > environments. I'm not 100% sure whether it still works on 14.04 but with > previous Ubuntu versions we were able to install GNOME destop > environment from the Software Center. What do You need a GNOME for? Just > because, whether You like it or not, along GNOME 2.x and 3.x we get > Xfce, Unity and kde. Now all You have to do is to choose a needed > environment on the login screen. Your mashine will perhaps become > heavier but You get a powerful playground.
Thanks for the hint with GNOME. I might try that out sometime (on a VM, because I will need to know how to undo stuff :P). In my particular situation, I was still running 12.04 on my Linux machine, and I didn't want to risk an upgrade at the time (when I tried to upgrade to Saucy a few months ago, it foobared the machine and I had to reinstall 12.04 from scratch again). One does use one's computer for various things, not for just testing the langpacks for 1 product. Certainly, testing if something crashes isn't something I'd do for an operating system that I depend on to do any other work whatsoever. So, I first tried a VM on my Windows machine, which has a bigger screen, but this resulted in bluescreens, so I had to do it on the Linux machine on Virtualbox, which gave me a tiny window, because it's an old laptop with a small screen. We also have to keep in mind that what seems easy to a developer like us isn't always easy for translators who don't know anything about coding - apart from using placeholders, obviously. I also didn't see any instructions on how to revert the language pack, should it actually crash. Setting the upgrades to "proposed" is pretty easy, but if you wish to upgrade the language pack only (e.g. because you depend on the OS you're currently messing with), you have to start using the commandline and to fiddle with config files. So, in the end, even if I had already been running Trusty, I would still have set up a virtual machine for this, because I don't want to foobar my primary OS. I do realize you can't just snap your fingers and have automated testing appear like magic, but it would be a great help to small localizing teams if you could look into coding something for this. >> I understand the need for ensuring that langpacks don't crash but surely >> there must be a simple way of checking for strings which might cause >> this automatically? I have no idea what CAN cause a langpack to crash >> Ubuntu but I imagine it's missing placeholders or code that has been >> inadvertently introduced. Surely this can be run as an automatic check >> and if not, the surely Canonical could just set up a machine to >> auto-test all langpacks and if any of them crash, to flag it to the >> locale team in question. > > Probably you are right, and probably it's about priorities. Can you (or > somebody else who reads this) file a wishlist bug? > Which would be the correct project on Launchpad to file the bug? -- ubuntu-translators mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
