patching core drupal files

Hi.

Yes, I too dislike to have to patching core files and modules,
but it is the only way to implement some features.

At now the patches do :

- patch for cache (common.inc and bootstrap.inc)
This is used only for url like /node, that must have different content upon the language(s),
but the url is only one.
Re-implementing the same feature of node call in localizernode module, for example,
we could avoid this patch, but the patch is necessary if you need multi-language support.
(I mean : if you want to see contents of different languages in the same page)

- patch for menu.
It is very simple, and it is more a bug correction.
It passes back the menu id when you insert a new one so that localizer
can insert the data correctly in localizertranslation table.
You can avoid this patch, but the you have to save again the menu item
to be sure that localizertranslation table is correctly populated.
It is only necessary when you insert a new menu item.

- patch for taxonomy
This implements dictionary and term translations.
At now, there is no other way to implement this.
in the next Drupal version (6) taxonomy translation will be possible
without patching only duplicating taxonomy trees.

If you don't need multi language support and don't use taxonomy,
you can avoid to patching the files.

Localizer 2.0 will work without patching core files.

Localizer v2.x is available now.