Main Menu

Language problems

Started by evilaro, February 07, 2012, 03:16:48 PM

Previous topic - Next topic

evilaro

Hello:

I am playing with this... in diferent combinations:

exiftool.exe -Description="aaaa áááá bbbb cccc" -Keywords="aaaa áááá bbbb cccc" -Caption-Abstract="aaaa áááá bbbb cccc" myimage.jpg


Looking at he result In bridge and using ExifTool,

-Keywords show the spaces so:                 aaaa bbbb aaaaa cccc dddd  aaaa     will show OK

-Description -Caption-Abstract
DO NOT show spaces                                will only show up to the first espace  so only  => aaaa
(after trying different combinations this problem has gone)

The three
-Keywords,-Description -Caption-Abstract

does not show accents             aaaa bbbb ááááá cccc dddd  aaaa     will show only up to the accents       => aaaa bbbb

How can I solve the problems
Can I substitute the accents with certain characters ????

Thanks a lot

Emilio

PS Looking at the error messages it states that Malformated UTF-8 characters
I undestand that I have to use this language... or change to it...
Really I do not have a clue on how to do it...

www.evilfoto.eu
*************

Phil Harvey

Hi Emilio,

FAQ number 10 should answer your question about the accents.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

evilaro


Hi Phil:

What can I say... perfect.

Thaks

Emilio

PS
In what planet is this UTF-8 language is spoken?
I had enought problems to learn Spanish and English
and now UTF-8





Quote from: Phil Harvey on February 07, 2012, 06:38:54 PM
Hi Emilio,

FAQ number 10 should answer your question about the accents.

- Phil
www.evilfoto.eu
*************

Phil Harvey

Hi Emilio,

Quote from: evilaro on February 08, 2012, 10:31:42 AM
In what planet is this UTF-8 language is spoken?
I had enought problems to learn Spanish and English
and now UTF-8

I think you are only kidding here, but just in case I will try to clarify this: UTF-8 is not a language.  It is an encoding for representing the character sets of various languages on a computer.  It extends the old ASCII encoding, which didn't support any international characters, and it replaces a whole bunch of various other encoding schemes such as Windows Latin1, Mac Roman, etc, which were incompatible and a great source of confusion.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

evilaro

Phil:

Sorry I was only kidding, but thanks for the clarification.
But then was not UNICODE the one that was supposed to do all this????

Thanks again
Emilio


>I think you are only kidding here, but just in case I will try to clarify this: UTF-8 is not a language.  It is an encoding for representing the character sets of various languages on a computer.  It extends the >old ASCII encoding, which didn't support any international characters, and it replaces a whole bunch of various other encoding schemes such as Windows Latin1, Mac Roman, etc, which were incompatible >and a great source of confusion.

www.evilfoto.eu
*************

Phil Harvey

Hi Emilio,

UTF-8 is a type of Unicode encoding (it actually stands for 8-bit Unicode Transformation Format).  What people once called "Unicode" is now known as UCS-2, where each character is exactly 2 bytes wide.  UCS-2 supports most of the commonly used characters, but due to the 16-bit limitation it cannot represent all Unicode characters.  The modern equivalent is UTF-16, which supports surrogate pairs to get around the 16-bit limitation.  UTF-16 and UTF-8 both support the full set of Unicode characters.

But I'm guessing you're more confused now after reading this post... :P

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

evilaro

Phil:

It clearer.... but not all...
Its good to know that the UNICODE idea is still there.

But 16 bit is like 65 000 characters ...
How many support the full UNICODE standard ???

Thanks

Emilio


Quote from: Phil Harvey on February 08, 2012, 12:20:44 PM
Hi Emilio,

UTF-8 is a type of Unicode encoding (it actually stands for 8-bit Unicode Transformation Format).  What people once called "Unicode" is now known as UCS-2, where each character is exactly 2 bytes wide.  UCS-2 supports most of the commonly used characters, but due to the 16-bit limitation it cannot represent all Unicode characters.  The modern equivalent is UTF-16, which supports surrogate pairs to get around the 16-bit limitation.  UTF-16 and UTF-8 both support the full set of Unicode characters.

But I'm guessing you're more confused now after reading this post... :P

- Phil
www.evilfoto.eu
*************

Phil Harvey

Quote from: evilaro on February 08, 2012, 03:00:09 PM
But 16 bit is like 65 000 characters ...
How many support the full UNICODE standard ???

Good question.  Currently, the full Unicode character set is about 110 000 characters.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).