Ermal reported issues when changes are made on VLAN parent interface
with this patch. He did other changes and interface_configure() will now
be able to re-create VLAN interface
This reverts commit 5bc623536d.
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>
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
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>
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
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>
The descriptions of each entry in an alias are stored in config.xml as a list delimited by "||". So you cannot have "||" in the actual description (or the description effectively splits into the next entry). Also you cannot start or end the description with "|" or it will be very confusing having the config with "|||" in it.
This code validates all that sort of invalid input.
firewall_aliases_import should have the same checks for reserved names as firewall_aliases_edit
This code should really be in a function in a common include file, but which one is the appropriate one?
For now I made the checks the same.
This enhancement allows the user to make a text file of IP addresses, IP subnets and/or IP ranges, like they have always been able to do, but with this they can put a description after each IP number and that description text will be saved in the alias. All existing functionality without specifying a description is unchanged, so it is backward-compatible.
This is handy when having aliases that are on all my pfSense boxes, I can make 1 text file, bulk import it on every system and now include descriptions of each chunk of IP address space.
Note: The artificial limit of 200 character descriptions is to catch the case where a user pastes a long list or IP addresses, but they are all on 1 line. An error message is given, rather than importing the 1st IP and considered the remaining ones as the description.
