| Server IP : 103.119.228.120 / Your IP : 3.137.159.134 Web Server : Apache System : Linux v8.techscape8.com 3.10.0-1160.119.1.el7.tuxcare.els2.x86_64 #1 SMP Mon Jul 15 12:09:18 UTC 2024 x86_64 User : nobody ( 99) PHP Version : 5.6.40 Disable Function : shell_exec,symlink,system,exec,proc_get_status,proc_nice,proc_terminate,define_syslog_variables,syslog,openlog,closelog,escapeshellcmd,passthru,ocinum cols,ini_alter,leak,listen,chgrp,apache_note,apache_setenv,debugger_on,debugger_off,ftp_exec,dl,dll,myshellexec,proc_open,socket_bind,proc_close,escapeshellarg,parse_ini_filepopen,fpassthru,exec,passthru,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,popen,show_source,proc_nice,proc_terminate,proc_get_status,proc_close,pfsockopen,leak,apache_child_terminate,posix_kill,posix_mkfifo,posix_setpgid,posix_setsid,posix_setuid,dl,symlink,shell_exec,system,dl,passthru,escapeshellarg,escapeshellcmd,myshellexec,c99_buff_prepare,c99_sess_put,fpassthru,getdisfunc,fx29exec,fx29exec2,is_windows,disp_freespace,fx29sh_getupdate,fx29_buff_prepare,fx29_sess_put,fx29shexit,fx29fsearch,fx29ftpbrutecheck,fx29sh_tools,fx29sh_about,milw0rm,imagez,sh_name,myshellexec,checkproxyhost,dosyayicek,c99_buff_prepare,c99_sess_put,c99getsource,c99sh_getupdate,c99fsearch,c99shexit,view_perms,posix_getpwuid,posix_getgrgid,posix_kill,parse_perms,parsesort,view_perms_color,set_encoder_input,ls_setcheckboxall,ls_reverse_all,rsg_read,rsg_glob,selfURL,dispsecinfo,unix2DosTime,addFile,system,get_users,view_size,DirFiles,DirFilesWide,DirPrintHTMLHeaders,GetFilesTotal,GetTitles,GetTimeTotal,GetMatchesCount,GetFileMatchesCount,GetResultFiles,fs_copy_dir,fs_copy_obj,fs_move_dir,fs_move_obj,fs_rmdir,SearchText,getmicrotime MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/local/ssl/local/ssl/share/doc/fribidi-1.0.2/ |
Upload File : |
Before release:
* Use gtk-doc?
* Implement fribidi_wcwidth()?
* Port fribidi-main.c to new API.
* help2man.
Implementation issues:
* Add API to get and pass on TypeLink*, to not allocate bidi levels.
Something like that. Also the UTF-8 stuff from pango/mini-fribidi.
* Explore vis2log.
* Clean caprtl2utf8 to do arbitrary charset conversion?
* add --output-charset.
* Update README, etc...
* Mix __attr... with DLLIMPORT?
* Update all files headers/footers. For c/h files, lib/fribidi-mirroring.[ch]
is always the reference.
* In fribidi_main.c reorder after line break.
* Change fribidi-main cmd-line parameters: --mirror --no-mirror... change the
defaults too.
* Add an option to fribidi_main.c to assume two consecutive returns as
paragraph separators.
* Add more tests. For:
- Checking that not removing explicit marks in analyze is not changing the
output in anyway.
- Tests with BN. Right now ^ is BN in CapRTL scheme.
- Test tables.
* indent: support function attributes and _PARAMS like things. Also
FRIBIDI_BEGIN_DECLS, and LIKELY.
* Cleanup gen.tab/gen-*.c files.
* Override pkgincludedir and append interface version. Should we go the GNOME
parallel install way?
* c2man: parse Author and Copyright from the whole file.
* Write texinfo documentation.
* Set up gnu.org web pages, and update the entry in Free Software Directory.
* Use gengetopt.
* Add FriBidiEnv functionality at compile time. Also, ifdef out the memory
cleanup stuff if asked to fail on memory allocation failure (xmalloc). When
this is done, FRIBIDI_GNUC_WARN_UNUSEDS can be turned off conditionally.
* Generate HTML and DVI documentation.
* Rewrite fribidi.spec.in
* Add make rules for lib/$(BUILT_SOURCES) to depend on gen.tab/ stuff?
* When called in interactive mode, fribidi cmd-line should greet, write
about copyrtight stuff, and shared-libs' version and Unicode version.
* Configure gen.tab/ with host=build to avoid cross-compiling table
generators.
* Replace test/run.tests with something better, Makefile foo, etc.
* Clean up README and NEWS, and check all files' headers. Write
gen.tab/README. Also add UniData license file.
From GNU Coding Standards:
* The distribution should contain a file named `README' which gives the name
of the package, and a general description of what it does. It is also good
to explain the purpose of each of the first-level subdirectories in the
package, if there are any. The `README' file should either state the version
number of the package, or refer to where in the package it can be found.
* Add ^L to all sources.