touch up text
fix up text
Fix broken links to dhcp6c.conf man page.
manpath FreeBSD+Ports no longer exits and needs to be replaced with FreeBSD+10.1-RELEASE+and+Ports
fix text
Welcome 2015
clarify message here after customer feedback, it wasn't meant to imply "only a reboot will re-enable" but that's how some people have read it.
Update service providers xml to sync with upstream
Regenerate Turkish mo
Update po from last pot
Update Turkish translation file from last version available on old translation server
Regenerate pfSense.pot
6RD Rapid Deployment is akin to ATM Machine, PIN Number, ... read: it's redundant. let's just call it 6RD Configuration.
outbound NAT can apply to any type of interface, make WAN-type specific reference generic
fix text, PPPoE Server, not VPN
update input_error description after changes for ticket #3491
s/removing/omitting/g for gateway monitor log entires. "Removing" is not necessarily correct, there are many circumstances where this runs where it wasn't there to begin with, and is potentially misleading.
get back to our standard RFC-defined capitalization of IPsec
fix typo
Add a BETA key for PBI signature check, this will be replaced by the final one before RELEASE. Ticket #3365
s/BSDP/ESF/
xhtml Compliancereplaced <br>, <br/> and </br> with <br />
update translate pt_BR gettext file
Update list of mobile service providers
Change string to "Maximum new connections per host / per second(s)"
Clarifying the setting's meaning.
As suggested by forum member "Senser" onhttps://forum.pfsense.org/index.php/topic,65472.msg356024.html#msg356024
Remove PBI scripts since it'll be installed dynamically by tools
Sync pbi_create with pcbsd, add required functions.sh
Cleanup- most languages simply need the ascii abreviation.
Ful country code and encoding was necessary for pt_BR.ISO8859-1, (Brazilian Portuguese), and since it was the first translation, I followed the same format.
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>
bug address
Machine Translation (Phase 1) Complete.
Next steps:- generate the .mo files and try loading it up- Japanese Native Speaker(s) sanity pass through (roughly 20% complete already)- Review by pfSense authors/community
Machine generation used Google Translate API, translate.google.com, and Mort Yao's goog le-translate-cli
Wrapped some parsing around the following utility by Mort Yao, https://github.com/soimort/google-translate-cli
first full machine run
workspot: great, but this process requires tedious re-running the program.
Next step: wrap the translation step in a timeout, and print some simple hook in the output so you can find it for the machine translation copy/paste dance
workspot: cleanup and continued translation
X-Generator: vim(1), awk(1), sed(1) - for real.
workspot: trying to speed up machine translation
workspot: pass through to correct minor syntax
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>Signed-off-by: Kiyo Takami <foof@blackskyresearch.net>
workspot: mechincal first pass
workspot: continuing with machine translation, several heavily repeated phrases scrutinized
workspot: plowing ahead with machine translation
workspot: continuing machine translation first pass
workspot: carp and interface bits, continued first pass machine translation
workspot: firewall, interfaces, still plowing through machine translation
workspot: RADIUS and Captive Portal messages, machine translations
encoding change, and wrapping up LDAP sections rough pass
continued cumulative machine translations
workspot: country names
jp syntax change
workspot, continuing to run through with rough human-augmented machine translation
workspot- plowing through with rough human-augmented machine translation
start by copying pt_BR locale
minor spelling correction for pfSense master branch
touch up text, s/nat/NAT/
fix text - s/occured/occurred/
Fix #3113, fix multiple english spell errors s/seperet/separat/
EAOrigin.pat - Traffic Sharping Layer 7
The EA Store is now Origin, Tested and works (for now) will make changes if i come to anything useful.
SWF
As said on the pFsense forum http://forum.pfsense.org/index.php/topic,62863.0.html It works and tested by me.
Remove wrongly added file in commit 75f457856a
Update pot file
update pfSense.pot file
add lines to pfSense.pot file update
be careful first 2 line already have a pfSense.pot file.
Update pt_BR translation
Update translation template
Move pot translation file to en/, default locale directory
Move Turkish translation files to tr/, the default locale directory
Add Turkish translation files, ticket #2986
Update translatio files
updated pfSense.pot
Move locale files from /usr/share to /usr/local/share
add Tusmobil provider info.
feature #2462
Update serviceproviders.xml to a newer version
Update service providers.xml to latest version
First steps for 3g serviceproviders support
o Move xml2array from rrd.inc to pfsense-utils.inc because it'll be used on non-rrd related placeso Add necessary require_once() calls to pfsense-utils.inc on places that are calling xml2array()o Add serviceproviders.xml, obtained from [1]...
Rename unknown.pat to any.pat pattern since that is what it really means. This pattern matches any traffic.
Second pass at updateing protocol definitions.
Update layer 7 protocol definitions and adding new regex definitions.
Add protocol definitions needed by ipfw-classifyd. Basically they are copied from the ipfw-classifyd pfPort which inherits them from l7-filter project on sf.net.
MFC missing font