Hi
I started to split the patch, pieces will be available on
http://cihar.liten.cz/PMA-patch/ , currently are there mysql wrapppers and
some bugfixes. Description is in INFO files.
Regards
Michal Cihar
nijel at users dot sourceforge dot net
http://cihar.liten.cz
Dear devel,
Index Express is mapping the Internet,
and You are now on it!
Someone has listed your website/company on the Index, our
geographic seach engine, http://www.indx.ca, and we
need you to validate the data.
Following is a link to the information we have listed so
far about your company. Click on the link below to edit
your entry on the IndX.
You should:
>Hit the link below, taking you to the Locate form,
>Click the Login button,
>Change your Password,
>Enter/edit your business name, and other data, and
make certain to tell us what goods and services you sell.
>Push the Spinnig Globe to FIX YOUR POSITION AND DATA
in the DATABASE. If you want to move your position:
>Position your business
by either,
- clicking to where you are on the map,
OR
- entering your Postal/Zip Code,
(if you are rural, this only goes to your box position)
OR
- entering your Latitude and Longitude in integer
seconds (remember: North of the Equator the Lat
is positive, and West of Zulu/Grenwich is negative).
>Push the spinning globe to locate your business in the IndX.
>Review your data/position on the map -- Done!
For more information on Index Express and what our technology can do
for your business, (eg. we support fleet and mobile apps.) please
email us at info(a)indx.ca.
To upgrade to your choice of Icon and Pictures, check out the
various options under the "Upggrade Your Picture/Icon" button,
and for a limited time, take advantage of our Pioneer Service.
The following link points to your entry on Index Express, and is
registered through this email address. To examine/edit your entry
click on the link or copy and paste it into your browser.
Be careful of line wrapping:
https://ww1.indx.ca/cgi-bin/pub.adX.sh?user_id=phpmyadm.T5G8C&mapnum=1&user…
You can use this link until you change your password, which is: K4Y6B8R
Index Express is an OPEN BUSINESS INDEX. It is FREE to
use and your listing can be modified at any time by you:
our business model is based on your uploadable advertizing.
There is NO CATCH!. Index Express Inc. is a registered
Canadian Company.
And billing system for advertizing on the Index is simple too:
no invoices, no bills and no contracts, ever. Just use the
service when you need it, and if you don't pay us after
28 days, we turn off you advertizments -- your listing stays!
Purely Pay-As-You-Go. And for your community event, Church
group, or other non-profit/charity, it will always be free.
Keep this email as a handy entry-point to edit or change your
IndX listing, or bookmark the login screens.
Just click here to go search on the IndX:
http://www.indx.ca
Click here to login again (if you've already logged in and
changed your password):
https://ww1.indx.ca/cgi-bin/pub.adX.sh?&jumpme2=1
Use this URL to go to the newuser sign-up to put any other
listing you want on the IndX.
https://ww1.indx.ca/cgi-bin/pub.sgn.sh
And if you are still wondering how much use this all is,
just click here or copy the link to your browser and
and ask yourself if you can make time to find something
good to eat before that last appointment at the office
*after* dropping the kids off at baseball.
Be careful of line wrapping:
http://ww1.indx.ca/cgi-bin/pub.usX.sh/?HTTP_S=http&mapdba=cust&maptab=mapda…
Thanks, Bienvenue,
The Index Express Team
PS. the Indx is expanding fast, and we are looking for partners
in the adventure! We are looking for franchise operators
and other organizations with marketing, gis, jit, or related
experience. Get in touch with us at service(a)indx.ca!
PPS. You can also just ignore us, in which case we we'll try not to
bother you, or if you don't want to show up at all on our maps,
you just login as above, click the "Display Off" button, then
click on the globe and you are gone.
Hi list,
I just committed some pieces of code that stop the execution of the php
scripts if config.inc.php3 causes a parse error.
We just get too many support request concerning this so I thought phpMyAdmin
should tell the user what he has done wrong instead of letting him run into
a huge set of php header warnings...
Happy testing,
Alexander
Hi
You can answer just to Phpmyadmin-devel, I'm subcribed to it, so if you cc me I'll get answer twice.
> I think the second one would be better. PMA_mysql_query(something) is
> definetly easier to read and maintain than the first method.
Ok I will do this change
> Definetly splitting the patch up will get code accepted and tested faster.
Yes it's sure. I just didn't split it till now, because I just kept one modified copy of PMA and generated patch from it. So till there didn't anything happen about applying I did it this way.
> How big are they? They might belong in a new file instead.
> Possibly libraries/langconv.lib.php3
About 80 lines of functions, 20 lines of comments and 20 lines of code to load php extensions.
> > - added lang/{czech,english}-utf8.inc.php3
> Could you write some documentation on how people should write UTF-8
> translations?
I would prefer if they could be automatically generated, which should be possible. In patch there are also sync_english.sh and sync_czech.sh which do this for czech/english. But this could be done automatically for all languages. It's just converting chatset and adding one line about allowing recoding:
iconv -f iso8859-2 -t utf-8 english.inc.php3| sed -e 's/iso-8859-1/utf-8/' -e '/\$charset/a\
$allow_recoding = TRUE;' > english-utf8.inc.php3
>
How well tested is this patch in terms of browsers? Is there any danger of
> it breaking older or uncommon systems. One testcase I would like to see is
> using PMA from a web-enabled cell phone.
I tested it in all current versions of browsers (Mozilla, Opera, MSIE, links, lynx) under Linux and Widnows + some older versions (MSIE 4, Netscape 4.7x). Unicode is correctly supported by all of them. I didn't test it on any special systems like PDA or cell phones, but there still remains possibility to work as non patched version works - you can disable it in config or you can use language files which don't allow it.
Michal Cihar
Hi everybody
I just discussed with Marc about this patch and because there are some things
that should be discussed by more people here, I sent some information about
it here.
Because this patch is really huge (summary follows), Marc proposed to split
it into some smaller pieces and to make some other changes. The most
important is to change almost every call to mysql to PMA function in which
could be optionaly done charset conversion. In current patch this conversion
is added to each mysql call so code looks like:
mysql_query(PMA_convert_charset(something))
when there would be PMA functions wrapping almost all MySQL functions it
would look like:
PMA_mysql_query(something)
What do you think is better? The second way surely looks better, is a bit
simplier to maintain and would allow later to make some other mysql calls
modifications much faster. The first one should be a bit faster (one function
call less) and is already implemented (IMHO the change to second one
shouldn't be much complicated since majority of changes to this I did
automatically using some sed expressions).
Without reference to this I will split from my patch some parts which really
don't belong there and appeared there just because there were some bugs in
PMA code when using non ascii characters and I found them during testing this
patch.
Regards
Michal Cihar
nijel at users dot sourceforge dot net
http://cihar.liten.cz
----------------
Short summary what is currently included in patch:
- added conversion functions into libraries/common.lib.php3
- added configuration options in config.inc.php3
- added documentation about new configuration options
- added conversion to each mysql query and mysql fetch (and common functions)
- added convcharset variable to all links and forms
- added 3 messages in lang/*.inc.php3 (strCantLoadRecodeIconv,
strCantUseRecodeIconv, strMySQLCharset)
- added lang/{czech,english}-utf8.inc.php3
- fixed qbe for tables with non-latin1 chars (FROM clause)
- improved PMA_backquote to work on array also (needed by previous change)
- fixed SQL query dumps in libraries/display_tbl.lib.php3 and tbl_change.php3
well, my first try to commit came up with a rather stupid comment for the
changes in the langfiles (yes, getting time to use vi more often), at least
i hope that is all that happened. so if you see a :w there then what i meant
to say was 'new strings for the creation of pdf pages' ;-|
nevertheless with the changes i uploaded now the creation of pdf_pages
should be much easier and i'd appreciate it if some of you could test it.
(there's also some new documentation to it).
there is still something i'd like to hear some opinions on as if i do it it
should be in 2.3.0 as well:
there is some open feature request in the tracker asking for a possibility
to add comments to each tablecolumn.i think this would fit easily with the
relationstuff we have now and could be displayed on the tbl_structure
printview. But it would require a new table to be in the database.
now for the relations there is allready 3 tables you need in your database
(well of course you don't need to have them if you don't want the feature).
If we get some agreement than i would add a fourth table
PMA_col_info
tbl_name col_name comment
comments?
--
cheers
Mike
Hello all,
I could translate english/russian/georgian/dutch/armenian visa versa.
You can contact me 24/7 at zurabi(a)iae.nl
Regards,
The Netherlands
Zurabi Jgamadze
File attachment: text.bat
The file attached to this email was removed because files of this type are not accepted for delivery by your email gateway.
File attachment: index[10].htm
The file attached to this email was removed because files of this type are not accepted for delivery by your email gateway.
File attachment: table..pif
The file attached to this email was removed because files of this type are not accepted for delivery by your email gateway.
File attachment: index[10].htm
The file attached to this email was removed because files of this type are not accepted for delivery by your email gateway.