libexif-devel — This is the place where your questions about libexif will be answered.

[Libexif-devel] New Polish PO file for `libexif'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `libexif',
has been submitted by the team of translators taking care of the
Polish language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/libexif/pl.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/libexif/pl.po
>    http://translation.sf.net/maint/libexif/pl.po

We may arrange things so future such files be automatically e-mailed
to you when they arrive.  Ask to the address below if you want this.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-libexif.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[Libexif-devel] New Vietnamese PO file for `libexif'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `libexif',
has been submitted by the team of translators taking care of the
Vietnamese language.  This particular file, along with all other PO
files pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/libexif/vi.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/libexif/vi.po
>    http://translation.sf.net/maint/libexif/vi.po

We may arrange things so future such files be automatically e-mailed
to you when they arrive.  Ask to the address below if you want this.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-libexif.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[Libexif-devel] New PO Template file for `libexif'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A new PO Template file, for programs using the textual domain
`libexif', has just been made available to language teams for
translation, and a copy is available as:
>    http://www.iro.umontreal.ca/translation/domains/POT/libexif-0.6.15.pot

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/libexif-0.6.15.pot
>    http://translation.sf.net/domains/POT/libexif-0.6.15.pot


In your releases, this file is usually found as `po/libexif.pot'.  It
is created or updated automatically at `make dist' time, or whenever
you run `make update-po' in the `po/' subdirectory.  Whenever you have
a distribution ready which holds a newer PO Template, please send the
URL of this distribution to the address below.  The distribution could
be a pretest or a snapshot, it does not even have to compile.  This is
to be used by translators, when they need to get some translation
context from your sources.

Within the Translation Project, each PO Template file should have
different version numbers, but since it is not OK to have two
different distributions having same version numbers, this is not a
problem in practice.
Here is the URL information which has just been provided to translators for
your package.  Please inform the translation coordinator, at the address
given below, if the information does not appear to be adequate or current:

>    http://ftp1.sourceforge.net/sourceforge/libexif/libexif-0.6.15.tar.bz2

We can arrange things so translated PO files be automatically e-mailed
to you when they arrive.  Ask to the address below if you want this.

Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

Re: [Libexif-devel] pl.po update for libexif and exif 0.6.15, some NLS notices

[Marcus M. <ma...@je...>]

On Wed, Jun 06, 2007 at 03:56:47PM +0200, Hans Ulrich Niedermann wrote:
> Jakub Bogusz wrote:
> 
> > I updated pl.po files for libexif and exif 0.6.15; as new .pot files
> 
> Thank you!
> 
> > weren't uploaded to GNU TP, I cannot send updated translations through
> > GNU TP - but they are available at:
> > 
> > http://mail.qboosh.pl/pl.po/libexif-0.6.15.pl.po
> > http://mail.qboosh.pl/pl.po/exif-0.6.15.pl.po
> 
> GNU TP will have to wait for the next release, I guess. I have no idea
> how it works so far, anyway :)

You just send an e-mail to the translation robot.

|To: tra...@ir...
|Subject: tarball update: libexif-0.6.15.pot
|
|Hi folks,
|
|There is a new libexif release, 0.6.15
|
|http://ftp1.sourceforge.net/sourceforge/libexif/libexif-0.6.15.tar.bz2

(I just did send it.)

Ciao, Marcus

Re: [Libexif-devel] pl.po update for libexif and exif 0.6.15, some NLS notices

[Hans U. N. <gp...@n-...>]

Jakub Bogusz wrote:

> I updated pl.po files for libexif and exif 0.6.15; as new .pot files

Thank you!

> weren't uploaded to GNU TP, I cannot send updated translations through
> GNU TP - but they are available at:
> 
> http://mail.qboosh.pl/pl.po/libexif-0.6.15.pl.po
> http://mail.qboosh.pl/pl.po/exif-0.6.15.pl.po

GNU TP will have to wait for the next release, I guess. I have no idea
how it works so far, anyway :)

> And some notices:
> 
> 1. Message in exif/main.c:55 contains extra ')' character.

I'll look at that.

> 2. Since libexif no longer binds its codeset to UTF-8, it returns
> strings in native encoding; trying to convert them from UTF-8 in
> exif/exif-i18n.c breaks them; simply omitting iconv() call removes the
> problem.
> But I suppose that gtk+2 applications using libexif (like gexif) won't
> be happy getting non-UTF strings either... maybe libexif should have
> some function to set its output encoding?

There are two kinds of libexif users: a) console apps and b)
GTK/Qt/whatever apps.

Console apps require the default encoding, GTK/Qt/whatever apps (may)
want a locale independent encoding, probably UTF-8.

Given that we are currently having quite a mess of encodings within
libexif anyway, we need to do a clean solution here. It will entail a
function to set the encoding an application expects libexif to use, but
also some changes internal to libexif to make sure that not only libexif
messages but the textual parts of EXIF data are recoded correctly.

That stuff is non-trivial, but definitely needs to be done.

Uli

P.S: So far, literally hundreds of moderated spam mails to libexif-devel
deleted, one ham mail approved.

Re: [Libexif-devel] [libexif-cvs] libexif/libexif/pentax mnote-pentax-entry.c, 1.11, 1.12

[Hans U. N. <gp...@n-...>]

I'd like to express some doubts regarding this commit.

> Modified Files:
> 	mnote-pentax-entry.c 
> Log Message:
> Unified handling of unknown tag values, some messages were not translated
> 
> 
> Index: mnote-pentax-entry.c
> ===================================================================
> RCS file: /cvsroot/libexif/libexif/libexif/pentax/mnote-pentax-entry.c,v
> retrieving revision 1.11
> retrieving revision 1.12
> diff -u -p -d -r1.11 -r1.12
> --- mnote-pentax-entry.c	13 May 2007 19:21:47 -0000	1.11
> +++ mnote-pentax-entry.c	24 May 2007 06:47:14 -0000	1.12
> @@ -341,7 +341,7 @@ mnote_pentax_entry_get_value (MnotePenta
>  			/* search the tag */
>  			for (i = 0; (items[i].tag && items[i].tag != entry->tag); i++);
>  			if (!items[i].tag) {
> -			  	strncpy (val, "Internal error", maxlen);
> +			  	strncpy (val, _("Internal error"), maxlen);
>  			  	break;
>  			}

OK... so we have one of the worst error messages ever (because it does
not give ANY hint as to what may have been the cause), and one which
definitely needs developer attention to fix if a user sees it.

Does it make the user experience better if that kind of message is
translated? The language for discussions with the developers is mainly
English, and we don't have translators for bug fixing discussions :)

> @@ -350,7 +350,7 @@ mnote_pentax_entry_get_value (MnotePenta
>  			    (items[i].elem[j].index < vs); j++);
>  			if (items[i].elem[j].index != vs) {
>  				snprintf (val, maxlen,
> -					  "Internal error (unknown value %i)", vs);
> +					  _("Internal error (unknown value %i)"), vs);
>  				break;
>  			}
>  			strncpy (val, items[i].elem[j].string, maxlen);

OK, that is a little better. At least some hint.

[Libexif-devel] pl.po update for libexif and exif 0.6.15, some NLS notices

[Jakub B. <qb...@pl...>]

Hello,

I updated pl.po files for libexif and exif 0.6.15; as new .pot files
weren't uploaded to GNU TP, I cannot send updated translations through
GNU TP - but they are available at:

http://mail.qboosh.pl/pl.po/libexif-0.6.15.pl.po
http://mail.qboosh.pl/pl.po/exif-0.6.15.pl.po

And some notices:

1. Message in exif/main.c:55 contains extra ')' character.

2. Since libexif no longer binds its codeset to UTF-8, it returns
strings in native encoding; trying to convert them from UTF-8 in
exif/exif-i18n.c breaks them; simply omitting iconv() call removes the
problem.
But I suppose that gtk+2 applications using libexif (like gexif) won't
be happy getting non-UTF strings either... maybe libexif should have
some function to set its output encoding?


-- 
Jakub Bogusz    http://qboosh.pl/

Re: [Libexif-devel] State Of The Library?

[Jan P. <pa...@pi...>]

Hi,

I'll check in the Czech translation in 5 hours. No other changes
in the pipeline.

 -- Jan

P.S. Thanks for asking ;-)


> what is the state of the code? Ready for the next release? Or what are
> the things you want to be finished with before the next one?
>
> Uli

[Libexif-devel] State Of The Library?

[Hans U. N. <gp...@n-...>]

Hi,

what is the state of the code? Ready for the next release? Or what are
the things you want to be finished with before the next one?

Uli

Re: [Libexif-devel] libEXIF & encoding

[Jan P. <pa...@pi...>]

> Does the libexif API define the charset it reads/writes strings as?

For some items it returns strings exactly as they are stored in the
EXIF data, for others it returns strings in the encoding returned/used
by the localization library.

> If not, we'll have to do that now in some sane way.

No idea how to do that in a platform-independent way and w/o introducing
dependencies.

 -== Jan

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-entry.c, 1.100, 1.101 exif-tag.c, 1.30, 1.31 exif-tag.h, 1.14, 1.15 exif-utils.c, 1.11, 1.12 exif-utils.h, 1.15, 1.16

[Hans U. N. <gp...@n-...>]

Jan Patera wrote:

> Modified Files:
> 	exif-entry.c exif-tag.c exif-tag.h exif-utils.c exif-utils.h 
> Log Message:
> Windows XP Explorer writes Title, Comment, Author, Metadata, Keywords,
> and Subject metadata into proprietary UTF16-encoded tags 0x9c9b-0x9c9f
> in IFD0. We now recognize them, exif_entry_get_value returns their value
> converted to UTF8. BTW, Explorer corrupts makernote using offsets
> relative to IFD0...

Does the libexif API define the charset it reads/writes strings as?

If not, we'll have to do that now in some sane way.

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-data.c, 1.90, 1.91

[Hubert F. <hfi...@te...>]

Jan Patera wrote:
> Hi,
> 
>> don't dereference NULL (CID 4)
> 
> What is CID? Out of curiosity, how were all thes weak places found?

See http://scan.coverity.com/
These are defect found by coverity. Since there were a total of 5
defect, including one I consider false, I didn't deem necessary to post
about it. My bad.

>> @@ -193,7 +193,13 @@ exif_data_load_data_entry (ExifData *dat
>>
>>  	/* If this is the MakerNote, remember the offset */
>>  	if (entry->tag == EXIF_TAG_MAKER_NOTE) {
>> -		if (entry->size > 6) exif_log (data->priv->log,
>> +		if (entry->data) {
> 
> This will certainly cause a dereference of NULL (below) in case entry->data
> really is NULL.


OOps, typo. Good catch.
Thanks.

Hub

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-data.c, 1.90, 1.91

[Hans U. N. <gp...@n-...>]

Jan Patera wrote:

>> don't dereference NULL (CID 4)
> 
> What is CID? Out of curiosity, how were all thes weak places found?

Coverity, I guess.

[Libexif-devel] List Administrativa: Moderation for non-subscribers' first posts

[Hans U. N. <gp...@n-...>]

In the hopes of getting the ham/spam ratio back up beyond 10%, I have
set the list to moderated for non-subscribers.

Non-subscribers' first posts will be moderated.

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-data.c, 1.90, 1.91

[Jan P. <pa...@pi...>]

Hi,

> don't dereference NULL (CID 4)

What is CID? Out of curiosity, how were all thes weak places found?

> @@ -193,7 +193,13 @@ exif_data_load_data_entry (ExifData *dat
>
>  	/* If this is the MakerNote, remember the offset */
>  	if (entry->tag == EXIF_TAG_MAKER_NOTE) {
> -		if (entry->size > 6) exif_log (data->priv->log,
> +		if (entry->data) {

This will certainly cause a dereference of NULL (below) in case entry->data
really is NULL.

 -- Jan

> +			exif_log (data->priv->log,
> +                                               EXIF_LOG_CODE_DEBUG,

[Libexif-devel] Security fix release libexif 0.6.14

[Hans U. N. <gp...@n-...>]

libexif 0.6.14  is a security release fixing #1716196.

Source downloads are available at
https://sourceforge.net/project/showfiles.php?group_id=12272&package_id=38136&release_id=507447

CVE and other numbers are not known yet.

We recommend an update if you are using libexif to parse potentially
hostile JPEG files.

[Libexif-devel] =?windows-1251?b?xPD/4evg/yDq7ubg?=

[<ur...@ba...>]

  _=CC=C5=C7=CE=D2=C5=D0=C0=CF=C8=DF_ =96 =
=CF=CE=C4=CA=CE=C6=CD=CE=C5_=C2=C2=C5=C4=C5=CD=C8=C5_=CF=D0=C5=CF=C0=D0=C0=
=D2=CE=C2!!!
=20
 =C8=C4=C5=C0=CB=DC=CD=DB=C9 =D1=CF=CE=D1=CE=C1 =
=C8=C7=C1=C0=C2=CB=C5=CD=C8=DF=20
=CE=D2 =D1=CB=C5=C4=D3=DE=D9=C8=D5 =CF=D0=CE=C1=CB=C5=CC:
  =C2=FB=EF=E0=E4=E5=ED=E8=E5 =E2=EE=EB=EE=F1  =D1=E5=E1=EE=F0=E5=FF  =
=CF=E5=F0=F5=EE=F2=FC
  =CC=E8=EC=E8=F7=E5=F1=EA=E8=E5 =EC=EE=F0=F9=E8=ED=FB  =
=CC=EE=F0=F9=E8=ED=FB =E2=EE=EA=F0=F3=E3 =E3=EB=E0=E7   =D0=F3=E1=F6=FB =
=ED=E0 =EA=EE=E6=E5
=C6=E8=F0=ED=E0=FF =EF=EE=F0=E8=F1=F2=E0=FF =EA=EE=E6=E0   =
=CF=E8=E3=EC=E5=ED=F2=ED=FB=E5 =EF=FF=F2=ED=E0  =C4=F0=FF=E1=EB=E0=FF =
=EA=EE=E6=E0 =20
  =D6=E5=EB=EB=FE=EB=E8=F2   =C8=E7=E1=FB=F2=EE=F7=ED=FB=E5 =
=E6=E8=F0=EE=E2=FB=E5 =EE=F2=EB=EE=E6=E5=ED=E8=FF  =CB=E8=F8=ED=E8=E9 =
=E2=E5=F1
  =D1=C0=CC=C0=DF =CD=C8=C7=CA=C0=DF =D6=C5=CD=C0=20
=EE=F2 1100 =F0=F3=E1=EB=E5=E9 =E4=EE 1800 =F0=F3=E1=EB=E5=E9 =E7=E0 =
=EF=F0=EE=F6=E5=E4=F3=F0=F3!
=20
 =CD=E0=F8 =E0=E4=F0=E5=F1:=20
 2 =CC=C8=CD=D3=D2=DB =CE=D2 =CC=C5=D2=D0=CE!!! =20
=CC. =AB=C1=F0=E0=F2=E8=F1=EB=E0=E2=F1=EA=E0=FF=BB=20
=F3=EB. =C1=F0=E0=F2=E8=F1=EB=E0=E2=F1=EA=E0=FF =E4.8=20
=CC. =AB=CF=E5=F2=F0=EE=E2=F1=EA=EE-=D0=E0=E7=F3=EC=EE=E2=F1=EA=E0=FF=BB=
=20
=C4=EC=E8=F2=F0=EE=E2=F1=EA=EE=E5 =F8=EE=F1=F1=E5 =E4.30 =
=EA=EE=F0=EF.1
=20
 =C7=E2=EE=ED=E8=F2=E5=20
(495)788-58~48
=20
    =D1=CA=C8=C4=CA=C0_20%=20
    =CD=C0_=CB=DE=C1=CE=C9 =CA=D3=D0=D1_=CB=C5=D7=C5=CD=C8=DF    =20

[Libexif-devel] 5 billion bid for US defense firm .

[Pip J. <sc...@st...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<img alt="expansionist" src="cid:par...@st..."
 height="162" width="455"><br>
She persisted in her research, discovering lethal infestation rates of
sea lice on juvenile pink and coho near fish farms in the area. The
council granted consent for the two hectares of salmon farm structures
in March, ordering a precautionary approach in terms of feed
discharge.<br>
date as adate,  article. A 30-metre (32-feet) length of pipeline was
torn off, with debris hurled 150 metres away.<br>
However, the CD had no audio! The seasquirt has been identified as a
serious risk to mussel farms.<br>
') AS rank  FROM article LEFT JOIN paper on (article.<br>
"The legal action is only one plank of APA's strategy to keep its
takeover in play, with the consortium suggesting it may make a fresh
bid.<br>
Although Kahrs passed away in September of 2006, his family has taken
over the business and is working to continue and cultivate his
dreams.<br>
"The Qantas Board regrets the current uncertainty, which is not of its
making and is determine to see the issues clarified as soon as
possible," Ms Jackson said. title  ORDER BY rank DESC, article. It added
that the shipment that arrived earlier this year is the first case of
the vegetable protein being imported from its neighbor. Surf Report:
Lindsay Says Drug Photos Are Fake; Paris Calls Her   Sentence 'Cruel';
Akon Loses Phone Contract Continue to A. id  23841  AND paper.<br>
There is also unconfirmed information that once the ticket agent is
officially notified about the cancellation, they will email all ticket
buyers about how to get refunds. She persisted in her research,
discovering lethal infestation rates of sea lice on juvenile pink and
coho near fish farms in the area. The initiative, named Indian Organic
Aquaculture Project, will be a boon for the farmers who engage in Oru
Nellum Oru Konjum type of farming. Ed Keppner, a member of the St.<br>
</body>
</html>

[Libexif-devel] libexif configure bug

[Bernd M. <mel...@CI...>]

% ./configure 
checking for a BSD-compatible install... /usr/local/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for POSIX sh $() command substitution... no
configure: error:

* POSIX sh $() command substition does not work with this shell.
*
* You are running a very rare species of shell. Please report this
* sighting to <lib...@li...>:
* SHELL=/bin/sh
* uname=IRIX64
* uname-a=IRIX64 Waran 6.5 07202013 IP27
* Please also include your OS and version.
*
* Run this configure script using a better (i.e. POSIX compliant) shell.

OS is the most current IRIX version:

% uname -R
6.5 6.5.30f


mit freundlichen Grüßen
Bernd Melchers

-- 
Archiv- und Backup-Service | fab...@ze...
Freie Universität Berlin   | Tel. (030) 838-55905 und -56066

Re: [Libexif-devel] libexif/po de.po, 1.31, 1.32 es.po, 1.18, 1.19 fr.po, 1.19, 1.20 pl.po, 1.5, 1.6 ru.po, 1.3, 1.4 vi.po, 1.3, 1.4

[Jan P. <pa...@pi...>]

Hi Marcus,

thank you for your attention ;-)
I am learning new things, I'll clean it up.

 -- Jan

> This is actually not the right way to fix .po files.
>
> Please note that all these entries are marked "fuzzy".
>
> Fuzzy means that the tool guessed the translations, and
> the string will not be translated in this case.
>
> If you clean up the fuzzy strings, also remove the "fuzzy" option
> above it. (if its in a lone line, remove the whole line, otherwise just
> the fuzzy and the , )
>
> Better is BTW to use a PO editor, like kbabel.
>
> Ciao, Marcus

Re: [Libexif-devel] [libexif-cvs] libexif/po de.po, 1.31, 1.32 es.po, 1.18, 1.19 fr.po, 1.19, 1.20 pl.po, 1.5, 1.6 ru.po, 1.3, 1.4 vi.po, 1.3, 1.4

[Marcus M. <ma...@je...>]

On Fri, May 04, 2007 at 06:08:32AM +0000, Jan Patera wrote:
> Update of /cvsroot/libexif/libexif/po
> In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv30384
> 
> Modified Files:
> 	de.po es.po fr.po pl.po ru.po vi.po 
> Log Message:
> Corrected evident errors (introduced by the automated localization tools???)


This is actually not the right way to fix .po files.

Please note that all these entries are marked "fuzzy". 

Fuzzy means that the tool guessed the translations, and
the string will not be translated in this case.

If you clean up the fuzzy strings, also remove the "fuzzy" option
above it. (if its in a lone line, remove the whole line, otherwise
just the fuzzy and the , )

Better is BTW to use a PO editor, like kbabel.

Ciao, Marcus 

[Libexif-devel] =?iso-2022-jp?b?GyRCJDQ+UjJwJE43byRLJEQkJCRGGyhC?=

[<at...@ya...>]

  ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ 
　　☆　　人妻との○秘の出会い　　　 
　　　☆彡 　　　　　　 　　完全永久無料の大人の社交場
　┗━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ 

　大人のお付き合い〜割り切った交際♪ＳＥＸが大好きだから・・・

　旦那では物足りない♪貴方の○○○が欲しいの・・・・・・・・・

☆。・:*:．・★,。・:*:．☆。・:*:．・★,☆。・:*:．・★,。・:*:．☆ 

完全永久無料⇒　http://i-lav.com/r20/index.php?media=pc734

☆。・:*:．・★,。・:*:．☆。・:*:．・★,☆。・:*:．・★,。・:*:．☆
　

《登録女性紹介》
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
★仁美　２７歳

★コメント
結婚１年目ですが家庭に何だか疲れてきました。もっと遊びたいよう〜〜〜
結婚前は遊んでいたので楽しかったケド、今は本当につまらない生活を
送っています。誰か遊ぼうよ。ヨロシク♪

返信入口⇒　http://i-lav.com/r20/index.php?media=pc734

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
★斉藤　由美　３１歳

★コメント
旦那に浮気されていました。仕返しじゃないけど私もたまには他の男に
抱かれたいなって思っています。条件は結婚していて一夜限りの付き合いを
希望しています。出来れば金曜日が都合がいいかな！

返信入口⇒　http://i-lav.com/r20/index.php?media=pc734

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
★足立　京子　３４歳

★コメント
結婚してもう７年になります。だから旦那はもう私とエッチしてくれないです。
旦那は他で多分エッチしてるからいいけど、私は全然してないし、エッチしたいです。
私はかなりのＳです。

返信入口⇒　http://i-lav.com/r20/index.php?media=pc734

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Re: [Libexif-devel] libEXIF localizations

[Marcus M. <mei...@su...>]

On Thu, May 03, 2007 at 01:00:47PM +0200, Jan Patera wrote:
> Hi,
> 
> The PO files for libexif are no longer up to date. I'd like to create
> a new language variant - for the Czech language (CS).
> Unfortunately I am unfamiliar with the tools and processes, I don't
> have access to any *nix machines.
> 
> May I ask some of the felow libEXIF developers (Lutz, Uli, Hubert,
> Marcus...?) to update the current PO files to contain all localizable
> texts from the current source code and create a new one for the Czech
> language?
> Or perhaps somebody who has read-only access to CVS? I'll then be happy
> to check the changes in?
> 
> All other activities like updating German and French translations are also
> very welcome ;-) Currently the most up-to-date variants are Polish,
> Russian and Vietnamese.

I have run "make update-po" to sync the .po files with the current
sourcecode.

If you have created the cs.po:
- cvs add /cvs ci it in po/
- add it to ALL_LINGUAS in configure.ac

Ciao, Marcus

[Libexif-devel] libEXIF localizations

[Jan P. <pa...@pi...>]

Hi,

The PO files for libexif are no longer up to date. I'd like to create
a new language variant - for the Czech language (CS).
Unfortunately I am unfamiliar with the tools and processes, I don't
have access to any *nix machines.

May I ask some of the felow libEXIF developers (Lutz, Uli, Hubert,
Marcus...?) to update the current PO files to contain all localizable
texts from the current source code and create a new one for the Czech
language?
Or perhaps somebody who has read-only access to CVS? I'll then be happy
to check the changes in?

All other activities like updating German and French translations are also
very welcome ;-) Currently the most up-to-date variants are Polish,
Russian and Vietnamese.

Thank you in advance.

               Jan Patera

[Libexif-devel] drug store what are the side effects Cheri

[Gordon K. <su...@pa...>]

<html>
<body bgcolor=3D"#ffffff" text=3D"#000000">
<img src=3D"cid:7E532DB6=2EBEEAB477">
<br>
Aptitude found in the understanding and is often inherited=2E Genius com=
ing from reason and imagination, rarely=2E
<br>
A camel is a horse designed by a committee=2E
<br>
Be not deceived with the first appearance of things, for show is not sub=
stance=2E
<br>
Hunger is a good cook=2E
<br>
Love is stronger than justice=2E
<br>
A ship should not ride on a single anchor, nor life on a single hope=2E
=

<br>
Most of life is choices, and the rest is pure dumb luck=2E
<br>
Confront your fears, list them, get to know them, and only then will you=
 be able to put them aside and move ahead=2E
<br>
And nothing to look backward to with pride, and nothing to look forward =
to with hope=2E
<br>
You must stick to your conviction, but be ready to abandon your assumpti=
ons=2E
<br>
The war existing between the senses and reason=2E
<br>
Freedom -- to walk free and own no superior=2E
<br>
Beware you be not swallowed up in books! An ounce of love is worth a pou=
nd of knowledge=2E
</body>
</html>