Hi,
I just want to report a small bug.
If I have a query with a field named "password", it is parsed as it was the
MySQL keyword PASSWORD, which is not the case.
e.g :
INSERT INTO inscrit
(pseudo,email,password,icq,homepage,hobby,occupation,ville) SELECT
username,user_email,user_password,user_icq,user_website,user_occ,user_intere
sts,user_from FROM montgallet2.users
is displayed as :
INSERT INTO inscrit( pseudo, email,
PASSWORD , icq, homepage, hobby, occupation, ville )
SELECT username, user_email, user_password, user_icq, user_website,
user_occ, user_interests, user_from
FROM montgallet2.users
Regards,
Jocelyn Fournier
Hi list,
I have some trouble with my E-Mail-Account rabus(a)bugfixes.info: I have not
recieved any mails sent to this address for 2 days.
I already wrote to my ISP and I hope this will be fixed real soon.
Also affected of this was my SF address because it forwarded all mails to
rabus(a)bugfixes.info. Furthermore I did not recieve any mails sent to our
mailing lists.
If I missed something important during the last to days, please mail to one
of these addresses
rabus(a)users.sourceforge.net (Should work now)
alex(a)bugfixes.info (Same ISP, but it works...)
derrabus(a)gmx.de
derrabus(a)t-online.de
Thanks,
Alexander
Robin Johnson wrote:
> Hi List.
>
> Marc Delisle wrote:
> > It's time for a /docs directory, with smaller documents.
> > Someone (Robin?) suggested to use XML or DocBook format.
> >
> > The only thing I will regret is searching with the browser in
> > Documentation.html. Another idea was to put the doc in a table located
> > in the pmadb, and we integrate a small search engine. But this would
> > not be good as users would need the doc to install the doc :)
> >
> > Maybe a splitted doc and a well-made index would make me happy :)
>
> Here is my proposal:
> We start a seperate directory in the CVS for the documentation, and
> inside it we have the master files in XML format, plus the scripts to
> build the HTML/PDF formats.
>
> We will still be generating a big Documentation.html file, but our
> sources will be seperated to make for easier editing. There will be a
> Documentation version where the sections are split up as well. All
> generated from the same XML data.
Mike's point was that the resulting doc would be too big to load, if he
adds screenshots for QBE explanations. Does the new structure address
this problem?
Do you mean that we would not put the source doc directory in the
distribution kits?
Also, some images will be common between languages, some won't (i.e.
screenshots).
>
> The XML format will basically be a structured XML document, in which
> some nodes will be able to have a limited set of HTML tags in them
> (bold, italitcs etc. NO structual tags). It will make heavy use of the
> XInclude standard to get seperate files.
> Rough file system structure idea for system:
> src/xslt/xml-big.xml
> src/xslt/html-big.xml
> src/xslt/html-split.xml
> src/xslt/html-common.xml
> src/xslt/pdf.xml
> src/xslt/docbook.xml
> src/english-iso-8859-1/master.xml
> src/english-iso-8859-1/top.xml
> src/english-iso-8859-1/requirements.xml
> src/english-iso-8859-1/introduction.xml
> src/english-iso-8859-1/installation.xml
> src/english-iso-8859-1/config.xml
> src/english-iso-8859-1/config/PmaAbsoluteUri.xml
> src/english-iso-8859-1/config/PmaAbsoluteUri_DisableWarning.xml
> src/english-iso-8859-1/config/Servers.connect_type.xml
> src/english-iso-8859-1/config/... (more files go here)
> src/english-iso-8859-1/config/Functions.xml
> src/english-iso-8859-1/faq.xml
> src/english-iso-8859-1/faq/1.1.xml
> src/english-iso-8859-1/faq/1.2.xml
> src/english-iso-8859-1/faq/...
> src/english-iso-8859-1/faq/5.1.xml
> src/english-iso-8859-1/faq/5.2.xml
> src/english-iso-8859-1/faq/...
> src/english-iso-8859-1/faq/7.3.xml
> src/english-iso-8859-1/howto.xml
> src/english-iso-8859-1/howto/qbe/...
> src/english-iso-8859-1/howto/(whatever other howtos get written)/...
> src/english-iso-8859-1/developers.xml
> src/english-iso-8859-1/credits.xml
> src/french-iso-8859-1/(same files as english, just with french content)
> src/images/...
> bin/... (scripts go here)
> output/xml-big/ (empty on CVS tree)
> output/html-big/ ("")
> output/html-split/ ("")
> output/pdf/ ("")
> output/docbook/ ("")
>
> (master.xml is the root file)
>
> I'll see about putting together a prototype idea over the weekend.
>
> This will allow us to finally have translated documentation as well :-)
> Plus maintaining just one little xml file for each part of the
> application is a lot easier.
>
>
>> You can do a distinct document (howto-qbe or whatever) with screenshots.
>> I am not familiar with the best way to structure the doc, but I guess
>> that Documentation.html (and .txt) is getting too big.
>>
>>> ok, we agreed that we would keep the doku in one file - was there also
>>> allready agreement to keep the howtos within the same file?
>>> reason is i just rewrote db_details_qbe quite heavily, so next thing
>>> i'll
>>> have to go over the docu that Marc wrote as a usage tip for this, and
>>> i'd
>>> like to do this with some nice screenshots - however if it stays in
>>> one page
>>> with the docu i won't as it would get too big to load then.
>>
> Make a new document for now, with screenshots in PNG format (saved in
> the images directory, use a unique naming system maybe
> howto-qbe-####.png).
>
>
--
Marc Delisle
Hi,
someone tell me if you can convert with sync_lang.sh the chinese files.
If no developer can, I will remove the 2 chinese lines from sync_lang.sh.
The chinese translator sends us the converted files.
--
Marc Delisle
Hi List,
Somebody was playing with the live CVS tree and changed the ownership of the
files badly, and broken my auto update script for it. I've fixed it now, but in
future could you just leave the tree alone ?
The script is there so we don't need to update the test copy by hand constantly.
It runs every 3 hours pulling the latest tree from CVS. It's been working
perfectly for the last 2 weeks, so I intend to leave it there, and make
everybodies life easier.
Thanks.
> Also, some images will be common between languages, some won't (i.e.
> screenshots).
>
this certainly is a problem. it could be solved if we could use SVG (as
those are just XML Files), but unfortunately this is not yet available
widely enough.
i can imagine we could do some script that will check wether to show an svg
or a normal file, so those that are able to view svg get a translated one,
those that can only view a jpg will get a english one. but i don't think we
should do any scripting in the howto - this should work without a webserver.
so what i think we should do is use english graphics, but then have small
numbers in the graphic which we use in the text and also have a table with
translations:
so imagine a picture with three buttons:
--
thisist | 1. Send
picture | 2. Cancel
withthe | 3. think about it
numbers |
if you want to send the query click on (1)
--
As everything is always on the same place i think people should be able to
find it if we just refer to it by number.
cheers
--
Mike Beck
mike.beck(a)users.sourceforge.net
Hi list
I've modified way how PMA creates links to MySQL documentation to allow using local copy of MySQL manual that can be downloaded from http://www.mysql.com/documentation/ (all HTML types are now supported). Now it uses function PMA_showMySQLDocu($chapter, $link). $link contains name of page/anchor that is being linked, $chapter is used only for "HTML, one page per chapter", for example, documentation for SELECT is at http://www.mysql.com/documentation/mysql/bychapter/manual_Reference.html#SE…, so $chapter should be Reference and $link should be SELECT.
If you have (or had) any questions to me, please be patient now, because of floods here, email service is now realy unreliable (I still miss plenty of emails since about 2002-07-31).
Michal Cihar
cihar(a)email.cz
> You can do a distinct document (howto-qbe or whatever) with
> screenshots.
> I am not familiar with the best way to structure the doc, but I guess
> that Documentation.html (and .txt) is getting too big.
>
> It's time for a /docs directory, with smaller documents.
> Someone (Robin?) suggested to use XML or DocBook format.
>
> The only thing I will regret is searching with the browser in
> Documentation.html. Another idea was to put the doc in a
> table located
> in the pmadb, and we integrate a small search engine. But this would
> not be good as users would need the doc to install the doc :)
>
> Maybe a splitted doc and a well-made index would make me happy :)
>
well let's leave the Documentation.html and just start removing bigger
chunks to seperate documents, but then still leave some Explanation - so it
ends up looking a bit like the answer from a searchengine, only showing
heading and a paragraph of explanation for each document and the link.
i decided that i'll still do some interface changes on _qbe before i do any
screenshots- first of all i want some pulldown for the =,>= etc. stuff like
i did in tbl_select - i think that makes things clearer, also i am thinking
of using a vertical approach to it - as soon as you use more than three
columns you have to scroll horizontaly at the moment which i dislike.
--
Mike Beck
mike.beck(a)users.sourceforge.net
ok, we agreed that we would keep the doku in one file - was there also
allready agreement to keep the howtos within the same file?
reason is i just rewrote db_details_qbe quite heavily, so next thing i'll
have to go over the docu that Marc wrote as a usage tip for this, and i'd
like to do this with some nice screenshots - however if it stays in one page
with the docu i won't as it would get too big to load then.
--
Mike Beck
mike.beck(a)users.sourceforge.net
