Re: [CODE4LIB] Call for Product Feedback: Nete

Whoops. A word. *ranging from how we'll do business all the way **to the product itself.

[CODE4LIB] Call for Product Feedback: Nete

Heya folks, I'm Timothy Tavarez - founder of a small startup in Colorado Springs, CO that is developing an ILS called Nete for public libraries. I'm hoping to get some early feedback on all sorts of things, ranging from how we'll do business all the way the product itself. Nete is in alpha, but

Re: [CODE4LIB] Best way to handle non-US keyboard chars in URLs?

On Feb 20, 2016 9:33 PM, "Stuart A. Yeates" wrote: > > 1) With Unicode 8, sign writing and ASL, the American / international > dichotomy is largely specious. Before that there were American indigenous > languages (Cheyenne etc.), but in my experience Americans don't usually >

Re: [CODE4LIB] Best way to handle non-US keyboard chars in URLs?

> > > 3) Who type un-shortened URLs any more? > > I'm looking for responses that solve this rather than dismiss Intuitive > URLs. > The question is what the use case you're trying to solve looks like. Is the goal typability because it's hand transcribed from a business card, knowing what the link

Re: [CODE4LIB] Best way to handle non-US keyboard chars in URLs?

i, On Monday, 22 February 2016, Chris Moschini wrote: > On Feb 20, 2016 9:33 PM, "Stuart A. Yeates" wrote: >> >> 1) With Unicode 8, sign writing and ASL, the American / international >> dichotomy is largely specious. Before that there were American

Re: [CODE4LIB] Best way to handle non-US keyboard chars in URLs?

Use en-wiki style disambiguation? Cheers Stuart On Saturday, 20 February 2016, Andy Kohler wrote: > > > > Interested to hear if there's a 4th, best option. > > > > I don't know about the broader issue - looking forward to that discussion! > But in this example at least,