mirror of
https://github.com/netsurf-browser/netsurf
synced 2025-02-08 02:24:41 +03:00
Vincent Sanders
67ded2a02a
This moves message loading out of netsurf_init into each frontend
The translated message loading is dependant on configuration of resource location in each frontend, additionally they should have the ability to deal with errors in this loading in a implementation specific manner. This also extends the message loading API to be capable of loading from an inline memory buffer instead of from a file.
…
…
…
…
…
…
-------------------------------------------------------------------------------- NetSurf README -------------------------------------------------------------------------------- This document should help point you at various useful bits of information. Building NetSurf ================== Read the QUICK-START document in the Docs/ directory for instructions. Creating a new port ===================== Look at the existing front ends for example implementations. The framebuffer front end is simplest and most self-contained. Also, you can contact the developers for help: http://www.netsurf-browser.org/contact/ Check out the developer documentation sources listed below too. Further documentation ======================= The Developer section of the web site has loads of info to get you started: http://www.netsurf-browser.org/developers/ General documentation on how NetSurf's code works can be found on the development wiki: http://wiki.netsurf-browser.org/Documentation/ The code style guide is here: http://www.netsurf-browser.org/developers/StyleGuide.pdf
Description
Languages
C
95.4%
C++
1.9%
HTML
0.8%
Makefile
0.6%
Python
0.4%
Other
0.7%