Free xsl software for mac

SyncPlaces 3.4.1 is a great addition to your computer as it will enhance your browser. It is actually a Firefox add-on that allows you to synchronise your bookmarks and passwords between different installations of Firefox (e.g. a browser at Home and another at Work).

It only works with Firefox v3 and above (but is compatible with older bookmark extensions). The synchronize feature requires your own Web or FTP server, which is used to store the bookmarks centrally, but there are a number of free servers you can safely use (see the Support section for details of at least one of these).

Using your own server means you get to keep you bookmarks private rather than storing them on a third party server who may analyse, probe and profile you, sell that data to others, or use it for their own nefarious purposes.

Major Features:

1. SyncPlaces also takes a backup of your current bookmarks before overwriting them with what is on the shared server. So you can restore this backup if it all goes wrong and you can also manually take your own backup at any time.
2. Bookmarks are typically stored in JSON format as this is ideal for the storage of all the bookmark information from the new Firefox Places system (e.g. tags, queries, and annotations).
   
3. You can also export/import or send/receive your bookmarks in XBEL format. XBEL is great for sharing bookmarks with other browsers or older versions of Firefox, or transforming with XSL to style your bookmarks so you can access them from any browser without installing the SyncPlaces extension.
   
4. Both passwords and the list of password exceptions may also be synchronised, and are automatically encrypted before sending to maintain privacy.
5. Options available include auto-send and receive whenever local bookmarks change and/or at regular intervals and/or a set time and/or at Firefox startup/shutdown.

Enhancements:

• Fixed: When switching between profiles synchronising on different folders the selected folder was not being changed, although the name displayed was.

Requirements:

• Mozilla Firefox

jsXe is a fast, intuitive, scalable, platform-independent XML editor. jsXe aims to provide end users and developers with an intuitive way of creating XML documents that is simple enough to deal with any XML document but flexible to allow the addition of support for XML document formats through the use of plugins.
Main features:
General
- Written in Java, so it runs on Mac OS X, Unix, OS/2, Windows, and VMS.
- XML documents are edited using views. jsXe allows for multiple views.
- Syntax highlighted source view (version 0.4 beta)
- Plugin interface that allows the addition of views without re-compiling
- Relatively good serialization of XML documents. Supports the option of formatting serialized XML documents or not formatting. Supports preserving whitespace in text.
- Allows opening and editing of multiple XML documents in one open window.
- Incremental parsing. Parsing the document and validation will be done automatically without having to continuously hit a validate/parse button.
- Support for validation of an XML document using DTDs and other forms of Schema.
- DTD/Schema introspection. Information in the DTD/Schema is used to allow users to add and edit nodes based on defined within the DTD/Schema.
- Internationalization. jsXe has support to easily create translations of menus and messages into your native language.
- Built-in completion support for XML Schema, XHTML, XSLT, and XSL:FO
Tree View
- Adding, deleting, and editing of Nodes in an XML document using context menus.
- Adding, deleting, and editing of attributes of an element node.
- Drag and Drop of XML nodes within the Tree view and to text editors.
Source View
- Text editing of the full XML source of any XML document
- Cut, copy, and paste and other limited features.

DSpace is a groundbreaking digital repository system, that captures, stores, indexes, preserves and redistributes an organizations research material in digital formats.
Research institutions worldwide use DSpace for a variety of digital archiving needs - from institutional repositories (IRs) to learning object repositories or electronic records management, and more.
DSpace accepts all manner of digital formats. Some examples of items that DSpace can accommodate are:
- Documents, such as articles, preprints, working papers, technical reports, conference papers
- Books
- Theses
- Data sets
- Computer programs
- Visualizations, simulations, and other models
- Multimedia publications
- Administrative records
- Published books
- Overlay journals
- Bibliographic datasets
- Images
- Audio files
- Video files
- eformatted digital library collections
- Learning objects
- Web pages
NOTE: DSpace is distributed and licensed under the terms of the BSD License.

Enhancements:
- (Scott Phillips) Fixed bug where users could not finish registering nor reset their password because the authentication method signatures were changed.
- Jay Paz (SF#1898241) Additional fixes to patch to enable reuse of methods.
- Added the ability to manage sessions with site wide alerts to prevent users from authenticating.
- Fixes a bug where the ability to edit an item durring workflow step 2 is not displayed.
- Jay Paz (SF#1898241) Add item Export from jspui and xmlui.
- Added easy support for google analytics statistics
- Added the ability for super admins to login as other users.
- Added an activity viewer to the Control Panel
- Fix for SF Bug #2082236 Subscription notification (sub-daily) no emails sent
- [2102580] William Hays: Duplicate Handle exception when replacing bitstreams
- [2102617] Sands Fish: X509Authentication fails to assign appropriate specialgroups
- (Sands Fish) Add "Select Primary Bitstream" functionality to submission workflow
- Guard against Community/Collection metadata having only whitespace characters and eliminate cases where null pointer exceptions would be thrown
- Improve DSIndexer logic in both branches to support removal of items from index when withdrawn from repository.
- (Sands Fish) Provides fix for AuthenticationUtil where users IDs are not properly compared.
- Fix NullPointerException cause by nullified Context object in LNI map item to new collection.
- Block Basic Authentication "details" from being exposed in dspace logs.
- (Bill Hays) Close InputStreamReaders explicitly to release any file handles back to OS.
- correct linking on pages when xmlui is the ROOT webapplication
- correct issue with sitemap redirection of mydspace uri.
- Add serlet-api to overlay wars to reduce compile time errors when adding classes
- Correct issues in feed generation
- XMLUI Adjust Advanced Search to use search properties from dspace.cfg.
- Correct bug in Body.toSAX where startElement is called instead of end element.
- Correct issue with libraries being excluded from wars
- Fix for SF bug #2090761 Statistics wrong use of dspace.dir for log location
- Fix for SF bug #2081930 xmlui hardcoded strings in EditGroupForm.java
- Fix for SF bug #2080319 jspui hardcoded strings in browse
- Fix for SF bug #2078305 xmlui hardcoded strings used in UI in xmlui-api
- Fix for SF bug #2078324 xmlui hardcoded strings used in UI in General-Handler.xsl
- SF patch #2076066 Review in jspui submission non-dc metadata
- SF Bug #1983859 added Foreign Lucene Analyzers to poms
- SF Bug #1989916: missing LDAP authentication key
- [1947036] Patch for SF Bug1896960 SWORD authentication and LDAP + [1989874] LDAPAuthentication
- pluggable method broken for current users
- Added copying of registration email template to 1.4 to 1.5 upgrade instructions
- Fix for SF bug #2055941 LDAP authentication fails for new users in SWORD and Manakin
- [1990660] SWORD Service Document are malformed / Corrected Atom publishing MIME types
- Updated installation and configuration documents for new statistics script, and removed references to Perl
- Fix for SF bug #2095402: Non-interactive Submission Steps dont work in JSPUI 1.5
- Fix for SF bug #2013921: Movement in Submission Workflow Causes Skipped Steps
- Fix for SF bug #2015988: Configurable Submission bug in SubmissionController
- Fix for SF bug #2034372: Resorting Search Results in JSPUI always gives no results
- Updates to Community/Collection Item Counts (i.e. strengths) for XMLUI.
- 1.5 upgrade instructions were missing Metadata Registry updates necessary to support SWORD.
- Fix various problems with resources potentially not being freed, and other minor fixes suggested by FindBugs
- Replace URLEncoder with StringEscapeUtils for better fix of escaping the hidden query field
- Fix #2034372: Resorting in JSPUI gives no results
- Fix #1714851: set eperson.subscription.onlynew in dspace.cfg to only include items that are new to the repository
- Fix issue where the browse and search indexes will not be updated correctly if you move an Item
- Fix problem with SWORD not accepting multiple concurrent submissions
- Fix #1963060 Authors listed in reverse order
- Fix #1970852: XMLUI: Browse by Issue Date "Type in Year" doesnt work
- Statistics viewer for XMLUI, based on existing DStat. Note that this generates the view from the analysis files (.dat), does not require HTML report generation.
- Fixed incorrect downloading of bitstream on withdrawn item
- Add JSPUI compatible log messages to XMLUI transformers
- Clean up use of ThreadLocal
- Improved cleanup of database resources when web application is unloaded
- Fix bug #1931799: duplicate "FROM metadatavalue"
- Fixed Oracle bugs with ILIKE operators and LIMIT/OFFSET clauses

Icecast is a streaming media server which currently supports Ogg streaming including the vorbis and theora codecs. Icecast can also handle other streams like AAC, NSV and MP3.
It can be used to create an Internet radio station or a privately running jukebox and many things in between. It is very versatile in that new formats can be added relatively easily and supports open standards for communication and interaction.

System requirements:
-

Enhancements
Character set support. Most non-Ogg streams (eg MP3) send metadata as Latin1 but it could be in other character sets. As icecast uses UTF-8, we need to convert to UTF-8 so that web pages and stream directories render correctly:
- Allow a per-mount setting. For when source clients do not indicate which character set is in use.
- a charset= parameter to the metadata request.
- Default for non-Ogg content is now Latin-1 (aka ISO-8859-1). Ogg content still uses UTF-8.
Authentication:
- Each mountpoint authentication is isolated so one mount authentication does not slow another mountpoint authentication down.
- XSL pages can require authentication.
- Add some sanity checks for incorrect settings.
Listening socket update:
- Allow multiple ports to be allocated which allow multiple shoutcast source clients to stream on the same icecast instance.
- No internal limit on the number of listen sockets that can be used.
- Allow for a listen socket to be marked SSL capable. While any client could connect on these, the idea is really for /admin requests.
- allow for a to bind to ipv4 and ipv6
XSL update:
- XSL pages include an xspf link for non-auth streams.
- XSL pages in both webroot and adminroot can take a mount= arg to limit which stats are transformed.
- XSL files can specify the content-type to return to the client. It is no longer fixed to html
Updates for stream directory handling:
- A stream is not registered with the directory until after the first minute has passed. some streams have been stuck in a connect/disconnect loop.
- Increase retry time on failure, if the stream add is rejected then it will be down to a misconfiguration so a long retry delay is performed.
- A YP server that is not responding is ignored for a while
- Updates for Win32. Newer versions of dependency libs (libxml2/libxslt/libcurl etc). Buffer overflow fixes when many streams are active
- Accept/Ban IP support. Now takes filenames for explicitly accepting or denying requests from specified IP addresses. Useful in cases where firewall access is not available. The files, if defined, are re-read automatically if updated.
- A Mountpoint is exported to the slaves even if no mount section is defined for it. You can still use the hidden setting to prevent that from happening.
- Relays handle redirection (HTTP 302) if one is received at startup.
- Automatically generate XSPF playlist like we do with M3U, the mountpoint extension is .xspf
- Header updates for proxy handling and certain clients like some shoutcast source clients and flash players.
- Added Kate/Skeleton codecs to Ogg handler.
- Various stats cleanups. Added some global stats (server ID, email contact etc).
- The streamlist passed from master to slave had a limited length, so if there were many streams then some could of been left out.
- Documentation updates.
- Relay startup/shutdown is cleaner.
- several build cleanups.
- several resource leaks and race conditions fixed

Logtalk 2.37.5 brings you canvenience of using such an object-oriented logic programming language that can use most Prolog implementations as a back-end compiler.

As a multi-paradigm language, Logtalk includes support for both prototypes and classes, protocols (interfaces), component-based programming through category-based composition, event-driven programming, and high-level multi-threading programming.

Major Features:

1. Separation between interface and implementation: Predicate directives (declarations) can be contained inside protocols (interfaces), which can be implemented by any object.
2. Parametric objects: Object identifiers can be compound terms containing free variables that can be used to parametrize object predicates. This allows us to interpret predicate clauses as providing instantiations of a parametric object identifier. I.e. through parametric object we can associate any number of methods with a compound term.
3. Support for both class-based and prototype-based systems: You may have, in the same application, class-based hierarchies (with instantiation and specialization relations) and prototype-based hierarchies (with extension relations). Moreover, fundamental language features such as protocols (interfaces) and categories (components) can be used simultaneously by classes, instances, and prototypes.
4. Support for multiple object hierarchies: No need to be constrained to a single, lengthy hierarchy rooted in some generic object.
5. Private, protected, and public inheritance: Logtalk supports private, protected, and public inheritance in a way similar to C++. Moreover, any entity relation can be qualified using a scope keyword. E.g. an object can privately implement a protocol, thus making all protocol declared predicates private.
6. Private, protected, and public object predicates: Set the scope of your object predicates to match your protocol design and let the runtime system enforce your choices.
7. Static and dynamic objects: Objects can be either static or dynamic. Static objects are defined in source files which are compiled and loaded in the same way as Prolog files. Dynamic object can be either defined in source files or created at runtime.
8. Static and dynamic object predicates: Any static object may contain both static and dynamic predicates.
9. Logtalk syntax extends standard Prolog syntax: Logtalk uses standard Prolog syntax with the addition of a few operators and directives for a smooth learning curve. Prolog code can be easily encapsulated inside objects with little or no changes. Moreover, Logtalk can transparently interpret most Prolog modules as Logtalk objects for easy reusing of existing code (e.g. libraries).
10. Event-driven programming: Predicates can be implicitly called when a spied event occurs, allowing programming solutions which minimize object coupling. In addition, events provide support for behavioral reflection and can be used to implement the concepts of pointcut and advice found on Aspect-Oriented Programming.
11. Component-based programming: Predicates can be encapsulated inside categories, which can be virtually imported by any object, without any code duplication and irrespective of object hierarchies. Thus, objects may be defined through composition of categories, which act as fine-grained units of code reuse. Categories may also extend existing objects. Categories can be used to implement aspects and mixin-like behavior without resorting to inheritance.
12. Multi-threading programming: High level multi-threading programming is available when running Logtalk with selected back-end Prolog compilers, allowing objects to support both synchronous and asynchronous messages. Independent and-parallelism and competitive or-parallelism are also supported. Easily take advantage of modern multi-processor and multi-core computers without bothering with the details of creating and destroying threads, implement thread communication, or synchronizing threads.
13. Multi-inheritance support: Logtalk supports multi-inheritance of both protocol and implementation. An object may implement several protocols and extend, specialize, or instantiate several objects. Multi-inheritance conflicts are solved implicitly by the Logtalk lookup algorithms or explicitly by using predicate directives.
14. Good performance: Logtalk code is compiled using the same technics that you use to write efficient Prolog code. In addition, Logtalk supports both static binding and dynamic binding (with method lookup caching), greatly improving performance. Benchmark results for some Prolog compilers are available here.
15. Close integration with the ISO Prolog Standard: Logtalk is designed for smooth integration with any Prolog compiler that conforms or closely follows the ISO Prolog Standard.
16. Compatible with most Prolog compilers: Logtalk interfaces with a specific back-end Prolog compiler via a minimal configuration file making it compatible with almost any modern compiler.
17. Automatic generation of XML documentation files: Logtalk automatically generates a documentation file in XML format for every compiled object, protocol, or category. The system includes all the necessary XSL(T) files and scripts to convert documenting files to (X)HTML and PDF.
18. Dynamic language: Logtalk is a dynamic language that allows hierarchies, objects, protocols, categories, and methods (predicates) to be freely created and modified at runtime. Other dynamic language features include support for meta-programming and both structural and behavioral reflection.