What OS are you on? Does this go away if you export a UTF-8 locale? or "C" 
locale?

I notice that at least in this email, that � is uFFFD "Replacement 
character" (http://www.fileformat.info/info/unicode/char/0fffd/index.htm). 
Something, somewhere, thinks that it's receiving a completely invalid 
character; if I had to guess, you're feeding latin1 to something that wants 
UTF-8. Maybe that something is tup itself; I don't know what encoding tup 
expects Tupfiles to be in, or if that changes based on the locale of the 
enclosing environment.

 - Zack

On Wednesday, April 22, 2015 at 9:11:12 AM UTC-4, Gavin Cannizzaro wrote:
>
> Hi everyone.... first-time poster here.
>
> Just when I'd given up looking for the perfect build tool, someone on HN 
> mentioned Tup.  I tried it and I loved it right away.  The last couple of 
> days I've been converting a project, working through various issues.  Now I 
> am stumped.
>
> Typical situation: I have a folder with a bunch of images that I want to 
> shrink into another folder, keeping the names.  This all works fine, except 
> that Tup seems to be conflicted about the filenames that contain non-ASCII 
> characters:
>
> * 771) site\static\images\full: shrinkimage 
> ..\..\..\../media/images\Am�rico-Hamlet.jpg Am�rico-Ha
> mlet.jpg 1920 x 80
>  *** tup errors ***
> tup error: File 
> 'D:\home\gavin\ws\local\site\static\images\full\Américo-Hamlet.jpg' was 
> written to
> , but is not in .tup/db. You probably should specify it as an output
>  -- Delete: 
> D:\home\gavin\ws\local\site\static\images\full\Américo-Hamlet.jpg
> tup error: Expected to write to file 'Am�rico-Hamlet.jpg' from cmd 9024 
> but didn't
>  *** Command ID=9024 ran successfully, but tup failed to save the 
> dependencies.
>
>
>
> Again, the command worked: the image was produced and with the correct 
> name.  But Tup stops after three such files because it thinks the target 
> file is supposed to have a different name, yielding the double warning 
> above.
>
> The filenames must contain these characters, and they pose no problems in 
> the bash script that I'm trying to replace.
>
> My rules are simple:
>
>
> include_rules
>
> MAX_WIDTH = 1920
> MAX_HEIGHT = x
> RETENTION= 80
>
> OPTS += $(MAX_WIDTH)
> OPTS += $(MAX_HEIGHT)
> OPTS += $(RETENTION)
>
> : foreach $(DOWNLOADED_IMAGES)\* |> shrinkimage %f %o $(OPTS) |> %B.jpg
>
>
>
> Any help is appreciated.
>
> Thanks,
> Gavin
>

-- 
-- 
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to