On 1/20/2015 10:59 AM, Rich Shepard wrote:
Well, yes and no, much to my chagrin, when using the copy command on
Ubuntu, I discovered files that would not copy as they used a different
encoding in the file name.
They displayed normally do to "naturalization", but when copied to a
NTFS formatted disk, refused.
On Tue, 20 Jan 2015, Paul D. Mirowsky wrote:
Are you using UTF-8?
I don't know much about your problem, but Googling shows there may be
According to that web page, UTF-8 is the default for sqlite3_open() and
sqlite3_open_v2(). In that case, having LANG=en_US.UTF-8 should not be a
reason why Base cannot establish the connection.
I eventually resolved the problem using "convmv" command.
convmv - converts filenames from one encoding to another.
The nice thing about this command is it does have a test mode and will
not change anything until you tell it to.
Hence, a command that runs properly, but cannot recognize a file name.
Another shot in the dark.
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: Base: Connecting to SQLite3 .db and Working With it · Fernand Vanrie
[libreoffice-users] Re: Base: Connecting to SQLite3 .db and Working With it · Andreas Säger
- [libreoffice-users] Re: Base: Connecting to SQLite3 .db and Working With it (continued)
Impressum (Legal Info)
: 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