issues
search
felipemoraes
/
warc-tools
Automatically exported from code.google.com/p/warc-tools
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
lib/private/plugin/python/warc_wrap.o: could not read symbols: Bad value
#108
GoogleCodeExporter
opened
9 years ago
1
lib/private/plugin/python/wrapper_wbloc.c - error: "_POSIX_C_SOURCE" redefined
#107
GoogleCodeExporter
opened
9 years ago
1
contrib/browser/browser.py and contrib/browser/readme have 'wrong' end-of-line character
#106
GoogleCodeExporter
opened
9 years ago
0
make wcsafe.o cause error
#105
GoogleCodeExporter
opened
9 years ago
0
Missing cunit for mingw
#104
GoogleCodeExporter
opened
9 years ago
0
warcvalidator seems slow
#103
GoogleCodeExporter
opened
9 years ago
0
How to checkout the source code?
#102
GoogleCodeExporter
opened
9 years ago
0
The C enumeration types should be available when using the java wrapper
#101
GoogleCodeExporter
opened
9 years ago
0
Missing documentation on how to use java wrapper
#100
GoogleCodeExporter
opened
9 years ago
0
warcdump outputs header to STDERR and body to STDOUT
#99
GoogleCodeExporter
opened
9 years ago
0
wrong word in manual
#98
GoogleCodeExporter
closed
9 years ago
3
test warc files does not validate at all
#97
GoogleCodeExporter
closed
9 years ago
3
SRS 89 — Assembly code and specific system features shall not be used in libwarc to ensure resulting code is widely portable across multiple target architectures
#96
GoogleCodeExporter
closed
9 years ago
3
SRS 88 — Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
#95
GoogleCodeExporter
closed
9 years ago
2
SRS 87 — The default compiler used for all Unix systems to build libwarc will be gcc v.3.4.4...
#94
GoogleCodeExporter
closed
9 years ago
1
SRS 86 — Libwarc shall not depend on a specific build tool in order to be built from source...
#93
GoogleCodeExporter
closed
9 years ago
1
SRS 85 — Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP
#92
GoogleCodeExporter
closed
9 years ago
1
SRS 84 — Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
#91
GoogleCodeExporter
opened
9 years ago
1
SRS 83 — Libwarc binary modules, ready to use binary commands and libraries...
#90
GoogleCodeExporter
opened
9 years ago
1
SRS 82 — Libwarc source code shall be released in the following archives...
#89
GoogleCodeExporter
opened
9 years ago
1
SRS 81 — Command line tools incorporating libwarc shall be atomic...
#88
GoogleCodeExporter
closed
9 years ago
1
SRS 80 — To ensure code portability on older computer architectures, Libwarc shall be compatible with any compiler conforming to the ANSI-C standard C89 revision
#87
GoogleCodeExporter
closed
9 years ago
2
SRS 79 — Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
#86
GoogleCodeExporter
closed
9 years ago
2
SRS 78 — Libwarc and associated tools shall be shipped with installers to "mod_warc" for Apache (v2.X) and Lighttpd (v1.4.X) servers
#85
GoogleCodeExporter
closed
9 years ago
2
SRS 77 — The code and documentation of libwarc shall be licensed to the community using an IIPC approved license, such as Apache 2.0 or BSD licence
#84
GoogleCodeExporter
closed
9 years ago
1
SRS 72 — Libwarc shall be shipped with a developer guide and useful examples
#83
GoogleCodeExporter
closed
9 years ago
1
SRS 76 — Patches implemented for third party projects shall be contributed and distributed to the appropriate community
#82
GoogleCodeExporter
closed
9 years ago
1
SRS 75 — Communication and support shall be provided to the open source community...
#81
GoogleCodeExporter
closed
9 years ago
1
SRS 73 — Libwarc shall be shipped with a number of ready-to-use command lines...
#80
GoogleCodeExporter
closed
9 years ago
1
SRS 74 — Utility and application level functionality of WARC Tools shall be made available to end users as command line tools...
#79
GoogleCodeExporter
closed
9 years ago
1
SRS 71 — Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
#78
GoogleCodeExporter
closed
9 years ago
1
SRS 70 — Libwarc shall be shipped with a manual and build scripts
#77
GoogleCodeExporter
closed
9 years ago
2
SRS 69 — Libwarc shall be developed on GNU/Linux, Fedora 7
#76
GoogleCodeExporter
closed
9 years ago
1
SRS 68 — Major revisions to the WARC ISO standard may lead to revisions of libwarc...
#75
GoogleCodeExporter
closed
9 years ago
1
SRS 67 — Libwarc shall be implemented to WARC v0.17.
#74
GoogleCodeExporter
closed
9 years ago
1
SRS 66 — It shall be possible for libwarc to be able to read, write and update WARC files at high speed...
#73
GoogleCodeExporter
closed
9 years ago
1
SRS 65 — It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
#72
GoogleCodeExporter
closed
9 years ago
8
SRS 64 — Libwarc and the bindings to its functionality shall enable the use of libwarc’s iterators described in SRS 16-20 to be used within Java v1.5...
#71
GoogleCodeExporter
closed
9 years ago
1
SRS 63 — Libwarc and the bindings to its functionality shall enable the use of libwarc’s iterators described in SRS 16-20 to be used within various dynamic languages and in Java v1.4 and earlier...
#70
GoogleCodeExporter
closed
9 years ago
1
SRS 62 — An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
#69
GoogleCodeExporter
closed
9 years ago
1
SRS 61 — A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI
#68
GoogleCodeExporter
closed
9 years ago
1
SRS 61 — A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI
#67
GoogleCodeExporter
closed
9 years ago
5
SRS 60 — A Python interface to libwarc shall be implemented using the SWIG wrapper
#66
GoogleCodeExporter
closed
9 years ago
1
SRS 59 — Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
#65
GoogleCodeExporter
closed
9 years ago
1
SRS 58 — Void, duplicate of SRS 79
#64
GoogleCodeExporter
closed
9 years ago
1
SRS 57 — WARC files in various test-states shall be provided that test the Jhove deliverables
#63
GoogleCodeExporter
closed
9 years ago
2
SRS 56 — WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
#62
GoogleCodeExporter
closed
9 years ago
3
SRS 55 — The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files
#61
GoogleCodeExporter
closed
9 years ago
5
SRS 54 — A magic number for WARC shall be created and incorporated in the “file” mime-type database, enabling the simple identification of WARC files via the Unix "file" command
#60
GoogleCodeExporter
closed
9 years ago
3
SRS 53 — Helper documentation for libwarc functionality shall be made available within the "HTTrack", "wget" and "curl" commands.
#59
GoogleCodeExporter
closed
9 years ago
1
Next