Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 6/06/2013 6:56, Lionel Elie Mamane wrote:
On Sat, May 25, 2013 at 05:54:03PM +0200, Andreas Mantke wrote:
Am 25.05.2013 17:35, schrieb Jesús Corrius:
     I can do it. Should I rename the extension-file thus it reflects
     the use only for Windows? And maybe a version number in the file
     name would a big value.
This is the default file name you get when you compile it. I guess we
can name it something like mysql-connector-windows-1.0.1. Does it
sound good?
yes. Could you do this and give me the new URL on dropbox. I'll do the
fun stuff on the extensions-site then ;-)
Currently, when one downloads, one gets a file named
"extension-file-for-windows" instead of "something.oxt". This confuses
users, which think there is not extension; LibreOffice's extension
manager will by default *not* propose it for installation since it is
not called "something.oxt". Especially for Windows users in the
default configuration where the native file manager (explorer) does
not show extensions by default, and does not give any way to change a
file's extension, this can be stumping.

Please rename the file on the extensions website.
there is also good news, Bernard Ribot reported on the issue

Hi,

I downloaded extension with Jesus Corrius url.
Download is OK.
Installation under Win 7 32bits with LO 4.0 and LO 4.1.0 beta1 is OK.
Extension works correctly.

Thanks,
Bernard Ribot

greetz

Fernand





Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.