Results for modules translation from Japanese to English

preload modules:
preload modules:

all php modules follow a common structure:
all php modules follow a common structure:

there are basically two ways to compile modules:
use the provided "make" mechanism in the ext directory, which also allows building of dynamic loadable modules.

**ライセンス:** lgpl v2.1 (api); gplv2 (gui and modules)
**licence:** lgpl v2.1 (api); gplv2 (gui and modules)

after you run buildconf, configure --help shows the following additional modules:
enables userland module --enable-cross_conversion book:

these constants are defined by the php core. this includes php, the zend engine, and sapi modules.
this includes php, the zend engine, and sapi modules.

use the provided "make" mechanism in the ext directory, which also allows building of dynamic loadable modules.
the second method is good for those who (for some reason) don't have the full php source tree available, don't have access to all files, or just like to juggle with their keyboard.

the following directory and file functions should be used in zend modules. they behave exactly like their c counterparts, but provide virtual working directory support on the thread level.
they behave exactly like their c counterparts, but provide virtual working directory support on the thread level.

this function is special to all dynamic loadable modules. take a look at the creation via the zend_get_module macro first:
the function implementation is surrounded by a conditional compilation statement.

for security reasons, you should not put your dynamic modules into publicly accessible directories. even though it can be done and it simplifies testing, you should put them into a separate directory in production environments.
if you compiled it into the php binary, omit the call to dl(), as the module's functionality is instantly available to your scripts.

for example, resources are used to store database links and file descriptors. the de facto standard implementation can be found in the mysql module, but other modules such as the oracle module also make use of resources.
to create a new resource you need to register a resource destruction handler for it.

\<ahelp hid=\"svx_pushbutton_rid_sfxpage_lingu_pb_lingu_modules_edit\"\>言語モジュールを編集するには、言語モジュールを選択し、\<emph\>編集\</emph\> をクリックします。\</ahelp\> \<link href=\"text/shared/optionen/01010401.xhp\" name=\"edit modules\"\>\<emph\>モジュールの編集\</emph\>\</link\> ダイアログが開きます。
\<ahelp hid=\"svx_pushbutton_rid_sfxpage_lingu_pb_lingu_modules_edit\"\>to edit a language module, select it and click \<emph\>edit\</emph\>.\</ahelp\> the \<link href=\"text/shared/optionen/01010401.xhp\" name=\"edit modules\"\>\<emph\>edit modules\</emph\>\</link\> dialog appears.