On 2012.05.23 14:08, Hans de Goede wrote:
> Right, going with option 2 is 100% ok with me :)
With the final votes in, I went ahead and pushed a commit that shall
ensure our sources are UTF-8.
Turns out that we only had 2 files that were actually UTF-8 (3 if you
count AUTHORS: core.c and sync.c)
Hi,
On 05/23/2012 01:09 PM, Pete Batard wrote:
> On 2012.05.23 11:25, Xiaofan Chen wrote:
>>> I think the problem is the © '(c)' sign in the headers, I see
>>> 2 possible solutions:
>>> 1) Stick to ASCII only, so replace '©' with '(c)'
>>> 2) Convert the files to UTF-8 in our git repo and tarbals
On Wed, May 23, 2012 at 6:25 PM, Xiaofan Chen wrote:
> On Wed, May 23, 2012 at 5:30 PM, Hans de Goede wrote:
>> Hi,
>>
>> In the Fedora libusbx packages we ship example/*.c as part of the
>> development documentation. ATM we run this script on these files
>> because they are not UTF-8:
>>
>> for
+1 for UTF-8
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint securi
On 2012.05.23 11:25, Xiaofan Chen wrote:
>> I think the problem is the © '(c)' sign in the headers, I see
>> 2 possible solutions:
>> 1) Stick to ASCII only, so replace '©' with '(c)'
>> 2) Convert the files to UTF-8 in our git repo and tarbals
>>
>> So what do you think is the best solution?
>
> I
On Wed, May 23, 2012 at 5:30 PM, Hans de Goede wrote:
> Hi,
>
> In the Fedora libusbx packages we ship example/*.c as part of the
> development documentation. ATM we run this script on these files
> because they are not UTF-8:
>
> for i in examples/*.c; do
> iconv -f ISO-8859-1 -t UTF-8 -o $i.
Hi,
In the Fedora libusbx packages we ship example/*.c as part of the
development documentation. ATM we run this script on these files
because they are not UTF-8:
for i in examples/*.c; do
iconv -f ISO-8859-1 -t UTF-8 -o $i.new $i
touch -r $i $i.new
mv $i.new $i
done
We would like
