=== issyl0 is now known as Guest33668 [16:35] hi CarstenG [16:35] Can I ask you 2 questions? [16:55] Hi Hannie [16:55] Yes, sure. [16:55] Hey, ok, here is question one [16:55] I have a screenshot conflict with figures: [16:56] 3.33 and 3.34 [16:57] where are you? [16:57] 3.33 was a marginschreenshot, but the accompanying text is now mixed with the one from 3.34 [16:57] precise-e2? [16:57] yes, precise-e2 [16:58] I have temporarily changed marginscreenshot to screenshot [16:58] This works, but the picture is no longer in the margin, of course [16:58] I think this happened after I made 3.34 smaller [16:58] one moment, I generate the pdf... [16:59] I hope you see it too, I still have to upload my latest nl.po [17:01] Yes, I see it. [17:02] any suggestions how to fix this, except making it a screenshot? [17:02] It looks like the position of 3.34 is moved upwards in the document... [17:03] in the en version it looks better. [17:03] do you have the screenshot command at the right place? [17:03] Yes, I tried to move the whole string up, but that was a disaster [17:04] Answer to your question: it is the same stringnumber as the English one [17:04] I translate the msgid in the same msgstr [17:06] You do not need to come with a solution right now. I will send you an email. [17:07] Question nr 2: I get an error now when I generate the pdf. This is due to the title page not found. But I wonder if that is the only error. [17:08] No, if the right title page is not found, the english one is used instead. [17:08] so there is probably another error. [17:09] It always says 1 error, but there can be more [17:10] I just do not see an error in figures 3.33 and 3.34 [17:12] What I'll do is this: I will send my latest nl.po to LP. You can see I changed marginscreenshot for 3.33 to screenshot [17:12] It is not a very elegant solution, so if you have a better one, please let me know. [17:14] well, you can use the optional argument "baselineskip" for the screenshot command, e.g [17:14] nscreenshot[-5\\baselineskip]{03-U1-naut-sync-icons.png} [17:15] \\marginscreenshot[-5\\baselineskip]{03-U1-naut-sync-icons.png} [17:15] right, I will try that and let you know if it works. Thanks again [17:15] you can play with the value, positive or negative [17:15] fun [17:15] But you should use this only for the final touch. [17:16] that sounds reasonable [17:16] We, Rob and I, have just finished the reviewing. [17:16] So, I really hope we can publish soon. I will contact Kevin about a few minor issues [17:17] see you [22:28] hi [22:30] what is the font used for the ccbysa ? it always throw me an error when I try to compile the quantal manual :] [22:40] godbyk, btw, for the index bug, it seems it's the "Hyperref options for print/screen versions" block who breaks it in quantal [22:41] Hey, YoBoY. [22:41] YoBoY: If you run the pkgs/install-pkgs.sh script from the raring branch, it will download and install the CC Icons font for you. [22:41] YoBoY: Which index bug? [22:43] no index page links [22:44] YoBoY: Ah, that's not a bug per se. [22:44] YoBoY: The hyperref package (which provides the links) and the xindy program (which handles the indexing), aren't completely compatible. [22:44] and the install-pkgs.sh is not donwloading anything :] [22:44] Namely, xindy doesn't know how to handle hyperref links in the index. [22:44] So to get them to work together, I had to disable the links in the index. [22:45] YoBoY: Are you running the install-pkgs.sh script from the raring branch? [22:45] ho, ok, I understand [22:45] The quantal and precise-e2 versions haven't been updated yet. [22:45] no, quantal [22:46] I haven't started to work on the raring branch yet [22:46] Give me a moment and I'll update the quantal script. [22:46] no rush [22:46] It's late here, I have to go to bed ;) [22:48] Okay, the quantal script should be updated now. [22:50] btw I worked a bit more to understand how all the spaces are working. My conclusion is Launchap is annoying with latex. It converts the [nbsp] in real nobreakspace (" " << this one) and that's the problem with polyglossia who think it's a normal caracter and add another nobreakspace :] [22:51] Yeah. [22:51] I don't know how launchpad work with translations but can't it convert the [nbsp] in ~ ? [22:51] The non-breaking space is equivalent to ~. [22:51] And you can have multiple ~~~ strung together. [22:51] I don't know. Launchpad does all of that automatically. [22:52] polyglossia works fine with a ~ [22:52] I don't think I have any control over it. [22:52] (I didn't even know about the [nbsp] and [nnbsp] tricks until you guys told me about it.) [22:52] :) [22:53] for application translations it's usefull, and this way we can't forget them [22:53] Yeah. [22:53] For LaTeX, I think the opposite is better: just forget them and let LaTeX handle it. :-) [22:53] who can tell is a " " is a " " or a " " :D [22:54] Exactly! [22:55] yes, we can think like that, "don't put them" but it's so hard to teach the translation rules to new translators, having different rules for different projects can be difficult. And the manual is a good start point for new translators [22:56] That's understandable. [22:56] I'll try to find someone from LP [22:56] But it seems like the manual has a lot of different things to learn anyway (i.e., LaTeX syntax) that wouldn't apply to translating application strings. [22:56] yes :) [22:57] So from my perspective, it's just one more small rule to learn. :) [22:57] we can also create a script to run before the make to convert everything :p [22:58] Yes. if necessary, we can run a script that removes all the various spaces around punctuation marks before compiling the French translation. [22:59] todo for me : ask launchpad what it's possible to do with these [nbsp] :) [22:59] I'll do that tomorrow [23:00] Cool. Let me know what you find out. [23:01] yes sure :) [23:01] thanks for your answers [23:02] bye :) [23:05] G'night!