please for now let's forget about updating po files in master (using
scripts/update-po). It does not make sense to differ them from QA_3_5
for now and it will ease merging translations back. Once we release 3.5
we can probably go back to usual procedure.
Michal Čihař | http://cihar.com | http://phpmyadmin.cz
It was a great gsoc session with PMA last time. I could not contribute it
for last few months(after gsoc) because I had my final year exam at
university. I'm willing to continue my contribution to phpMyadmin as a non
gsoccer. Are there any remaining ideas to continue with ajaxification of
the PMA. If so I like to open a discussion on them and continue with them.
L G Thilanka Kaushalya
Computer Science & Engineering,
University of Moratuwa,
Connect with me at,
Gmail : lgtkaushalya(a)gmail.com
Twitter : @thilanka_k
Facebook : Thilanka Kaushalya
Yahoo : lgtkaushalya(a)yahoo.com
Blog : http://coders-view.blogspot.com/
I'm not sure what is happening between these branches but please wait
before merging QA_3_5 into master until the situation is fixed.
The usual recipe of
git merge -X ours QA_3_5
does not seem to work.
have we ever discussed the two different behaviors for 'More'?
- in the menu tabs, 'More' appears only if forced by the window size
- in the table structure, it is forced (contains various index links)
Someone with a larger screen could prefer to see her screen filled
As you might recall from the PHPExcel licensing discussion
Fedora people were investigating a possible licensing concern with the
tcpdf library we bundle. Nothing has come of that with Fedora, but
apparently the SuSE people have found something they don't like. The
user ChrisWi asked about it in the IRC channel and provided a link to
their bugtracker: https://bugzilla.novell.com/show_bug.cgi?id=736698 --
which requires a login, so he also provided the following text summary:
** begin paste **
phpMyAdmin 18.104.22.168 (and presumably many earlier versions as well) contains
tcpdf. This package claims to be LGPL-3.0+ licensed but contains the
YOU CAN'T REMOVE ANY TCPDF COPYRIGHT NOTICE OR LINK FROM THE
GENERATED PDF DOCUMENTS.
As the LGPL-3.0+ incorporates by reference the GPL-3.0+, sections 7 and
the GPL-3.0+ are relevant:
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
Accordingly, it may be possible to point out to tcpdf upstream that the
additional term that they apply may be viewed as a 'non-permissive
and that you wish to exercise your rights under the GPL-3.0+ to remove that
term from downstream distributions.
If upstream are unwilling to engage in meaningful discussion or take the
that the additional restriction is per se not part of the license
because it is
above the license and not incorporated into it, tcpdf should be dropped.
** end paste **
Now again, as I'm sure you're aware, we're not responsible for making
the distributions happy, but it's also in our best interest to try to
resolve these things. Looks to my non-lawyer eye like this is something
to push back on the tcpdf folks. Again, if I'm understanding correctly,
the problem is the additional line added that "YOU CAN'T REMOVE ANY
TCPDF COPYRIGHT NOTICE OR LINK FROM THE GENERATED PDF DOCUMENTS."
Additionally, Google provides a lot of results of people questioning
seems to be the best discussion. A discussion regarding the inclusion in
went so far as to bring up the dubious legal position of putting a
(tcpdf) copyright notice on the work of others.
From the tcpdf forums link, it appears the author has no interest in
changing this. To be fair to tcpdf, the only place I see his notice in
the generated PDF is the "PDF Producer" field of the file properties. I
think that's reasonable, but I think the part that concerns the SuSE
folks is the having a non-OSI-endorsed clause appended to a license; if
every project would do that it would be a nightmare to maintain. But
that's just my interpretation.
I've signed up for a Novell account, but I'm still not authorized to
view the bug report directly. At the moment, aside from the gentleman in
IRC, we have no line of communication to them or way of getting updates
on their internal discussion.
Thanks for your thoughts on this...
Currently the doc says
Number of rows displayed when browsing a result set. If the result
set contains more rows, "Previous" and "Next" links will be shown.
Due to  I suggest this:
Number of rows displayed when browsing a result set and no LIMIT
clause is used. If the result set contains more rows, "Previous" and
"Next" links will be shown.
I believe that an explicit LIMIT in the query has priority over MaxRows;
this is the current behavior.
Welcome to the first beta release for phpMyAdmin 3.5.0; here are the
major new features:
* browse-mode improvements
** grid editing
** remember recent tables
** remember last sort order by table
** flexible column width
** reorder columns
** more compact navigation bar
* AJAXification of many operations
* reorganised server status page, with server monitoring
* improved support for stored routines, events and triggers
* openGIS support
* zoom-search in table search
* Drizzle support
* improved ENUM/SET editor
Details will appear on http://phpmyadmin.net. In a hurry? you can visit
http://sourceforge.net/projects/phpmyadmin to download.
Marc Delisle, for the team