Public bug reported:
Project names in the Library should only contain us/ascii with no
spaces, as the project_name is used in the URL for the font. The project
name from the font family name by running the latter through a series of
preg_replace, trim and iconv functions.
This breaks for fonts family names that consist entirely of non-us/ascii
characters. The create font form needs additional validation and
functionality to ensure that this is the case. There are a number of
potential fixes.
1) Simply generate the project_name by running the family name through a
URL encoder.
2) Add validation to the create font family form that only allows
us/ascii in the Family Name field. Validate the family name on the
client side and the server side.
3) Add a Project URL field. As the Member enters text into the Family
Name, update the Project URL in real-time using the same server-side
algorithm. Before submission, validate that the Project URL begins with
at least one alphanumeric character. Allow the Member to set the Project
URL as some other desired transliteration else if e.g. the font family
name consists only of non-us/ascii characters.
** Affects: openfontlibrary
Importance: Critical
Status: Confirmed
** Changed in: openfontlibrary
Importance: Undecided => Critical
** Changed in: openfontlibrary
Status: New => Confirmed
** Changed in: openfontlibrary
Milestone: None => 0.3
** Description changed:
Project names in the Library should only contain us/ascii with no
spaces, as the project_name is used in the URL for the font. The project
name from the font family name by running the latter through a series of
preg_replace, trim and iconv functions.
This breaks for fonts family names that consist entirely of non-us/ascii
characters. The create font form needs additional validation and
functionality to ensure that this is the case. There are a number of
potential fixes.
1) Simply generate the project_name by running the family name through a
URL encoder.
2) Add validation to the create font family form that only allows
us/ascii in the Family Name field. Validate the family name on the
client side and the server side.
3) Add a Project URL field. As the Member enters text into the Family
Name, update the Project URL in real-time using the same server-side
algorithm. Before submission, validate that the Project URL begins with
- at least one alphanumeric character.
+ at least one alphanumeric character. Allow the Member to set the Project
+ URL as some other desired transliteration else if e.g. the font family
+ name consists only of non-us/ascii characters.
--
You received this bug notification because you are a member of Open Font
Library Developers, which is subscribed to Open Font Library.
https://bugs.launchpad.net/bugs/782824
Title:
Font uploader does not validate project name as ascii characters
Status in Open Font Library:
Confirmed
Bug description:
Project names in the Library should only contain us/ascii with no
spaces, as the project_name is used in the URL for the font. The
project name from the font family name by running the latter through a
series of preg_replace, trim and iconv functions.
This breaks for fonts family names that consist entirely of non-
us/ascii characters. The create font form needs additional validation
and functionality to ensure that this is the case. There are a number
of potential fixes.
1) Simply generate the project_name by running the family name through
a URL encoder.
2) Add validation to the create font family form that only allows
us/ascii in the Family Name field. Validate the family name on the
client side and the server side.
3) Add a Project URL field. As the Member enters text into the Family
Name, update the Project URL in real-time using the same server-side
algorithm. Before submission, validate that the Project URL begins
with at least one alphanumeric character. Allow the Member to set the
Project URL as some other desired transliteration else if e.g. the
font family name consists only of non-us/ascii characters.
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework.admins
Post to : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework.admins
More help : https://help.launchpad.net/ListHelp
