Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sed: RE error: illegal byte sequence #63

Closed
GoogleCodeExporter opened this issue Aug 18, 2015 · 5 comments
Closed

sed: RE error: illegal byte sequence #63

GoogleCodeExporter opened this issue Aug 18, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Aug 18, 2015

What steps will reproduce the problem?
1. clone repo
2. ./configure
3. make

What version of the product are you using? On what operating system?

latest version 7.3.300+

Please provide any additional information below.

On osx I've some troubles compiling vim, this because this file: 
runtime/tools/efm_perl.pl

em_perl.pl contains an UTF-8 char but the file isn't encoded correctly (?) 

So I got:

perlpath=`./which.sh perl` && sed -e "s+/usr/bin/perl+$perlpath+" 
../runtime/tools/efm_perl.pl 
>/usr/local/src/vim/HEAD/share/vim/vim73/tools/efm_perl.pl
sed: RE error: illegal byte sequence
make[1]: *** [installtools] Error 1

My locale is correctly UTF8

LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL="en_US.UTF-8"

My fix at the moment is:

iconv -c -t UTF-8 ./runtime/tools/efm_perl.pl > ./runtime/tools/efm_perl.pl

Original issue reported on code.google.com by daddyez...@gmail.com on 23 Apr 2012 at 10:33

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Aug 18, 2015

efm_perl.pl is encoded as latin1, not UTF-8.

Original comment by vega.james@gmail.com on 23 Apr 2012 at 11:47

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Aug 18, 2015

Original comment by lech.lor...@gmail.com on 8 Jul 2012 at 11:27

  • Changed state: WontFix
@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Aug 18, 2015

I'm sorry mr. lech is this OSX users discrimination or what??

we also have utf8 locales, and because of your latin1 outdated crap I can't use 
vim at my job.. BECAUSE I CAN'T COMPILE IT!  and it's your problem ignoring LC 
vars.. definitely not OS problem or package maintainer.

Original comment by knisliu...@gmail.com on 19 Jul 2012 at 11:05

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Aug 18, 2015

Non ASCII characters are only used in a comment.

Replacing them with ASCII characters makes the file
runtime/tools/efm_perl.pl both a valid latin1 and valid utf8 file.
I think it's safer to fix it this way rather than encoding the file in utf8.

See attached patch.

Original comment by dominiqu...@gmail.com on 20 Jul 2012 at 8:07

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Aug 18, 2015

Original comment by brammool...@gmail.com on 25 Jul 2012 at 2:51

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.