Hi,
On 8/13/2014 1:18, Paul wrote:
Hi Mark,
...
Normally, localization is done by having a plain text file with all the
application strings in it, and this file is simply copied and each
string translated for each different language. Then at run time the
application knows which locale it is
Hi Werner,
On Wed, 13 Aug 2014 08:09:31 +0200
Werner werner...@gmx.ch wrote:
Hi,
On 8/13/2014 1:18, Paul wrote:
Hi Mark,
...
Normally, localization is done by having a plain text file with all
the application strings in it, and this file is simply copied and
each string
Hi :)
There is a separate mailing list which might be able to offer suggestions.
Our mailing list for international translators and co-ordinating between
the different languages is
l...@global.libreoffice.org
(lower and upper-case don't matter = it's just to help human readers make
more sense of
Hi Joel,
Well, on the one hand, changing to a database does mean learning
databases, and putting in a certain amount of time to develop it,
although you should be able to pull in the data from the spreadsheet.
There's also no clear gain, if the spreadsheet works for you, what do
you gain by going
Hey Paul,
First thanks for your thoughts :)
Well, on the one hand, changing to a database does mean learning
databases, and putting in a certain amount of time to develop it,
although you should be able to pull in the data from the spreadsheet.
There's also no clear gain, if the
Hi Joel,
On Fri, 8 Aug 2014 10:53:12 -0700
Joel Madero jmadero@gmail.com wrote:
So my thought was to have three tables -
*Table - BooksRead*
Author
Book
SeriesName (can allow Null because most books are not in a series)
Pages
*Table - Series*
SeriesName (not unique per row)
On Fri, Aug 8, 2014 at 11:32 AM, Paul paulste...@afrihost.co.za wrote:
Hi Joel,
On Fri, 8 Aug 2014 10:53:12 -0700
Joel Madero jmadero@gmail.com wrote:
So my thought was to have three tables -
*Table - BooksRead*
Author
Book
SeriesName (can allow Null because most books are not
Hi Joel,
On Fri, 8 Aug 2014 11:38:19 -0700
Joel Madero jmadero@gmail.com wrote:
On Fri, Aug 8, 2014 at 11:32 AM, Paul paulste...@afrihost.co.za
wrote:
Hi Joel,
On Fri, 8 Aug 2014 10:53:12 -0700
Joel Madero jmadero@gmail.com wrote:
So my thought was to have three
Yes, but what would go into the Series table? SeriesName and BookName
are already in the BooksRead table, and the read flag just indicates
that it is in the BooksRead table.
So the Series Table would have all books in a series and this way I could
query the next book to be read in a series.
Hi Joel,
On Fri, 8 Aug 2014 12:02:55 -0700
Joel Madero jmadero@gmail.com wrote:
Yes, but what would go into the Series table? SeriesName and
BookName are already in the BooksRead table, and the read flag just
indicates that it is in the BooksRead table.
So the Series Table
Hey Paul,
In this case, one book would be duplicated, and duplication is
usually a bad idea.
It would be better to put all the books into a single Books table.
I'm here to learn so I'll take your advice and do a single table.
Then if I set up some kind of a report that told me the
Hi Mark -
So crazy, I found your email response on my phone but for the life of me I
can't find it in either gmail or thunderbird (makes me concerned I'm losing
emails :( )
That being said I figured I'd just reply to your comments. First thanks so
much for taking the time to respond. As you
Hi Joel,
In addition to the below, you'll need to think about what database you
want to use. With Base, you can use the built-in HSQLDB, but from all
reports you really don't want to do that. I'd suggest setting up
something like PostgreSQL or MariaDB on your machine, and using that
with Base as
Hi Joel,
please don't think in reading the documentation like wasted time but an
invested time. It can really help to learn the basis, which I'm sure will be
useful for ever, specially what is learned about SQL. And IMO without at
least a quick read not easy even to ask for help.
With the
On 08/08/2014 03:30 PM, m.a.riosv wrote:
Hi Joel,
please don't think in reading the documentation like wasted time but an
invested time. It can really help to learn the basis, which I'm sure will be
useful for ever, specially what is learned about SQL. And IMO without at
least a quick read not
On 08/08/14 16:23, Paul wrote:
Hi Joel,
In addition to the below, you'll need to think about what database you
want to use. With Base, you can use the built-in HSQLDB, but from all
reports you really don't want to do that. I'd suggest setting up
something like PostgreSQL or MariaDB on your
16 matches
Mail list logo
