Excel.vim

Post by a3n » Fri, Oct 10, 2014, 2:17 PM UTC

rtpg wrote: post #10

deadweight3 wrote: post #8

Earlier quoted context omitted.

I hate this sentiment. I speak English and French and have limited amount of time to hack on software I'm giving away for free. My day job consists entirely in English. I have neither the experience, nor the inclination for internationalization of software. Don't like, don't use it. Or fork it, and add it yourself, because obviously you have more free time than I have.

the thing is if you build for unicode support from the start these conversations don't need to be had. The problem is not enough people treat text as a black box from the start (I can understand unwillingness to support bigger things like RTL)

Post by yzzxy » Fri, Oct 10, 2014, 2:33 PM UTC

ygra wrote: post #2

»Works best on excel files that contain English characters only.« That's a quite sad statement to make nowadays. I guess the old binary format might be worse regarding character sets, but at least the newer ones should use Unicode exclusively which makes this a very odd restriction.

Post by michaelmior » Fri, Oct 10, 2014, 2:38 PM UTC

izacus wrote: post #12

deadweight3 wrote: post #8

Earlier quoted context omitted.

I hate this sentiment. I speak English and French and have limited amount of time to hack on software I'm giving away for free. My day job consists entirely in English. I have neither the experience, nor the inclination for internationalization of software. Don't like, don't use it. Or fork it, and add it yourself, because obviously you have more free time than I have.

It's one thing to internationalize software. That's hard. But not being able to handle UTF-8 in 21st century is downright shameful. The notion of non-ASCII characters in user Excel documents IS NOT something rare even for English speaking nations. There are tons of people with foreign names, addresses and other personal information which is commonly stored in Excel documents. And the funny thing is: it's usually not…

Post by pyre » Fri, Oct 10, 2014, 2:43 PM UTC

deadweight3 wrote: post #8

ygra wrote: post #2

»Works best on excel files that contain English characters only.« That's a quite sad statement to make nowadays. I guess the old binary format might be worse regarding character sets, but at least the newer ones should use Unicode exclusively which makes this a very odd restriction.

I hate this sentiment. I speak English and French and have limited amount of time to hack on software I'm giving away for free. My day job consists entirely in English. I have neither the experience, nor the inclination for internationalization of software. Don't like, don't use it. Or fork it, and add it yourself, because obviously you have more free time than I have.

  # for non-English characters
  def getRealLengh(str):
      length = len(str)
      for s in str:
          if ord(s) > 256:
              length += 1
      return length

          for val in shn.row_values(n):
              try: val = val.replace('\n',' ')
              except: pass
              val = isinstance(val,  basestring) and val.strip() or str(val).strip()
              line += val + ' ' * (30 - getRealLengh(val))
          vim.current.buffer.append(line)

Post by boomlinde » Fri, Oct 10, 2014, 2:50 PM UTC

deadweight3 wrote: post #8

ygra wrote: post #2

»Works best on excel files that contain English characters only.« That's a quite sad statement to make nowadays. I guess the old binary format might be worse regarding character sets, but at least the newer ones should use Unicode exclusively which makes this a very odd restriction.

I hate this sentiment. I speak English and French and have limited amount of time to hack on software I'm giving away for free. My day job consists entirely in English. I have neither the experience, nor the inclination for internationalization of software. Don't like, don't use it. Or fork it, and add it yourself, because obviously you have more free time than I have.