Re: [Wireshark-dev] QT translation: lock keyboard shortcut terms?

2016-04-04 Thread Uli Heilmeier 
Am 04.04.16 um 08:07 schrieb Michal Labedzki:
> Please note that some translations (not Wireshark only!) translate
> arrow keys names (Up, Down, Left, Right).
> For example: Polish. (I think it based on the fact that Enter,
> Backspace, Shift, Ctrl, Alt, PrintScreen, Insert, Esc, etc. has
> English name on the button, but arrows have only arrows (pictogram),
> so it is better to translate them. So I am ok to lock all shortcut
> without those with arrow and also if someone requests something... Let
> me think... we should ask Russian, Chinese, etc. what they have on the
> keyboard?

Fair enough.
I've checked some qt_XX.qm files coming with Qt:
--
/var/tmp/qt_cs.ts:Down
/var/tmp/qt_cs.ts-Dolů
--
/var/tmp/qt_de.ts:Down
/var/tmp/qt_de.ts-Runter
--
/var/tmp/qt_hu.ts:Down
/var/tmp/qt_hu.ts-Le
--
/var/tmp/qt_ja.ts:Down
/var/tmp/qt_ja.ts-↓
--
/var/tmp/qt_ko.ts:Down
/var/tmp/qt_ko.ts-아래
--
/var/tmp/qt_pl.ts:Down
/var/tmp/qt_pl.ts-Dół
--
/var/tmp/qt_ru.ts:Down
/var/tmp/qt_ru.ts-Вниз
--
/var/tmp/qt_zh_CN.ts:Down
/var/tmp/qt_zh_CN.ts-Down


Therefore I think there is no need to translate the terms manually.

However Qt doesn't provide qt_xx.qm files for all languages we have in
Transifex (at least my Qt installation). But for every language where we
have active contributions.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] QT translation: lock keyboard shortcut terms?

2016-04-04 Thread Uli Heilmeier 
Hi Alexis,

> How can we prevent this?
> * Remove keyboard shortcuts from the wireshark_xx.ts file (if feasible)
> 
> After a check, yes, it is possible to remove (via Qt Design for example
> "Close"
> diff --git a/ui/qt/main_window.ui b/ui/qt/main_window.ui
> index 021d788..881f6c7 100644
> --- a/ui/qt/main_window.ui
> +++ b/ui/qt/main_window.ui
> @@ -817,7 +817,7 @@
>  Close this capture file
> 
> 
> -Ctrl+W
> +Ctrl+W
> 
> 
>  false
> 
> and after it is remove from ts file
> 

Sounds good. I would vote for removing the terms from the ts files.

If no one complains I will upload a patch with fixed ui file in the next days.

> * Establish a review process (like Gerrit) for translation files
>
> It is possible to have "Reviewer" on Transifex, if you are interresed and
> can add you to reviewer group for check german translation
>

Keeping the automatic sync (without review) is ok for me when we've
removed the shortcuts from ts file.

Cheers
Uli
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Anders Broman 
Hi,
Thanks Graham that fixed it. I was running the build (separate build dir) on my 
localized repo where I had been doing nmake builds before. Cleaning that up 
(clean distclean maintainer-clean)
Fixed the problem. I’m pretty sure I did clean on it before starting though.

Actually, just tested on my Wireshark dir, clean does not remove the generated 
files distclean does…
Best regards
Anders

From: wireshark-dev-boun...@wireshark.org 
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice
Sent: den 4 april 2016 15:26
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Current master not compiling



On 4 April 2016 at 12:05, Anders Broman 
> wrote:
Hi,
I'm also facing issues on MSVC 2015 and Cmake

 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214): error 
C2065: 'yyscan_t': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214): error 
C2146: syntax error: missing ';' before identifier 'scanner' 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215): error 
C2065: 'YY_BUFFER_STATE': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215): error 
C2146: syntax error: missing ';' before identifier 'in_buffer' 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215): error 
C2065: 'in_buffer': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(235): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(243): error 
C2065: 'in_buffer': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(243): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(250): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(256): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(319): error 
C2065: 'in_buffer': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(319): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(320): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]


   "C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
   "C:\Development\wsbuild64\ALL_BUILD.vcxproj.metaproj" (default target) 
(2) ->
   "C:\Development\wsbuild64\ui\ui.vcxproj.metaproj" (default target) (113) 
->
   "C:\Development\wsbuild64\ui\ui.vcxproj" (default target) (165) ->
 C:\Development\ewireshark\trunk\ui\text_import.c(909): error C2065: 
'yyscan_t': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(909): error C2146: 
syntax error: missing ';' before identifier 'scanner' 
[C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(909): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1021): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1027): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1029): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1031): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]

But dfilter is built with lemon isn't it? Flex is Cygwin 2.5.39-1 and there's 
not any newer version available...

On Windows, using CMake, I had to delete a lot of lex detritus grammar.[c|h], 
xxx.c, xxx_lex.h in my repo to get rid of the above errors.

I used git clean -dfx, maybe

Re: [Wireshark-dev] QT translation: lock keyboard shortcut terms?

2016-04-04 Thread Alexis La Goutte 
Hi Uli,


On Fri, Apr 1, 2016 at 8:27 PM, Uli Heilmeier  wrote:

> Hi list,
>
> At the moment the translation source files ui/qt/wireshark_xx.ts contains
> all the keyboard shortcuts (e.g. like 'Ctrl+Home'). Therefore these terms
> are also listed in Transifex.
>
> However these terms are translated "automatically" with the qt_xx.qm
> files. Doing a manually translation breaks the display of the shortcuts in
> the UI (s.
> https://www.wireshark.org/lists/wireshark-dev/201511/msg00101.html).
>
> I did the mistake to translate the terms some month ago and another
> member of the German Transifex team has done the same mistake this week.
>
I have the member to contact you before...


>
> How can we prevent this?
> * Remove keyboard shortcuts from the wireshark_xx.ts file (if feasible)
>
After a check, yes, it is possible to remove (via Qt Design for example
"Close"
diff --git a/ui/qt/main_window.ui b/ui/qt/main_window.ui
index 021d788..881f6c7 100644
--- a/ui/qt/main_window.ui
+++ b/ui/qt/main_window.ui
@@ -817,7 +817,7 @@
 Close this capture file


-Ctrl+W
+Ctrl+W


 false

and after it is remove from ts file

* Lock the terms (non writeable) in Transifex (if feasible)
>
Sorry, it is no possible (only can add translator note : "DON'T TRANSLATE
!")

> * Establish a review process (like Gerrit) for translation files
>
> It is possible to have "Reviewer" on Transifex, if you are interresed and
can add you to reviewer group for check german translation



> At the moment the translation is synced automatically (also for master-20).
>
> Any opinions?


> Cheers
> Uli
>
Regards,
Alexis


> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Guy Harris 
On Apr 4, 2016, at 4:05 AM, Anders Broman  wrote:

> But dfilter is built with lemon isn't it?

Lemon *and* Flex.

What happens if, for example, you remove all the following files:

epan\dfilter\scanner.c
epan\dfilter\scanner_lex.h
epan\diam_dict.c
epan\diam_dict_lex.h
epan\dtd_parse.c
epan\dtd_parse_lex.h
epan\dtd_preparse.c
epan\dtd_preparse_lex.h
epan\radius_dict.c
epan\radius_dict_lex.h
epan\uat_load.c
epan\uat_load_lex.h
plugins\mate\mate_parser.c
plugins\mate\mate_parser_lex.h
plugins\wimaxasncp\wimaxasncp_dict.c
plugins\wimaxasncp\wimaxasncp_dict_lex.h
text2pcap-scanner.c
text2pcap-scanner_lex.h
ui\text_import_scanner.c
ui\text_import_scanner_lex.h
wiretap\ascend.c
wiretap\ascend.h
wiretap\ascend_scanner.c
wiretap\ascend_scanner_lex.h
wiretap\k12text.c
wiretap\k12text_lex.h

and then try doing a rebuild?

For users on UN*Xes, that's

epan/dfilter/scanner.c
epan/dfilter/scanner_lex.h
epan/diam_dict.c
epan/diam_dict_lex.h
epan/dtd_parse.c
epan/dtd_parse_lex.h
epan/dtd_preparse.c
epan/dtd_preparse_lex.h
epan/radius_dict.c
epan/radius_dict_lex.h
epan/uat_load.c
epan/uat_load_lex.h
plugins/mate/mate_parser.c
plugins/mate/mate_parser_lex.h
plugins/wimaxasncp/wimaxasncp_dict.c
plugins/wimaxasncp/wimaxasncp_dict_lex.h
text2pcap-scanner.c
text2pcap-scanner_lex.h
ui/text_import_scanner.c
ui/text_import_scanner_lex.h
wiretap/ascend.c
wiretap/ascend.h
wiretap/ascend_scanner.c
wiretap/ascend_scanner_lex.h
wiretap/k12text.c
wiretap/k12text_lex.h

For autotools users, "make maintainerclean", followed by re-running autogen.sh, 
re-running configure, and rebuilding should suffice.  For nmake users, "nmake 
-f Makefile.nmake maintainerclean" and rebuilding should suffice.  I'm not sure 
what the equivalent would be for CMake.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Graham Bloice 
On 4 April 2016 at 12:05, Anders Broman  wrote:

> Hi,
> I'm also facing issues on MSVC 2015 and Cmake
>
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214):
> error C2065: 'yyscan_t': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214):
> error C2146: syntax error: missing ';' before identifier 'scanner'
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214):
> error C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215):
> error C2065: 'YY_BUFFER_STATE': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215):
> error C2146: syntax error: missing ';' before identifier 'in_buffer'
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215):
> error C2065: 'in_buffer': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(235):
> error C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(243):
> error C2065: 'in_buffer': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(243):
> error C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(250):
> error C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(256):
> error C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(319):
> error C2065: 'in_buffer': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(319):
> error C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>  C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(320):
> error C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
>
>
>"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>"C:\Development\wsbuild64\ALL_BUILD.vcxproj.metaproj" (default
> target) (2) ->
>"C:\Development\wsbuild64\ui\ui.vcxproj.metaproj" (default target)
> (113) ->
>"C:\Development\wsbuild64\ui\ui.vcxproj" (default target) (165) ->
>  C:\Development\ewireshark\trunk\ui\text_import.c(909): error
> C2065: 'yyscan_t': undeclared identifier
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>  C:\Development\ewireshark\trunk\ui\text_import.c(909): error
> C2146: syntax error: missing ';' before identifier 'scanner'
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>  C:\Development\ewireshark\trunk\ui\text_import.c(909): error
> C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>  C:\Development\ewireshark\trunk\ui\text_import.c(1021): error
> C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>  C:\Development\ewireshark\trunk\ui\text_import.c(1027): error
> C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>  C:\Development\ewireshark\trunk\ui\text_import.c(1029): error
> C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>  C:\Development\ewireshark\trunk\ui\text_import.c(1031): error
> C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>
> But dfilter is built with lemon isn't it? Flex is Cygwin 2.5.39-1 and
> there's not any newer version available...
>

On Windows, using CMake, I had to delete a lot of lex detritus
grammar.[c|h], xxx.c, xxx_lex.h in my repo to get rid of the above errors.

I used git clean -dfx, maybe check first with git clean -dnx to see what
will be deleted.

On Windows at least, I suspect this may be down to the difference between
quotes and angle brackets in includes.  We've been down this road before.

I'm not sure how the lex detritus got there, it didn't come back after the
build.

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe:

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Anders Broman 
Hi,
I'm also facing issues on MSVC 2015 and Cmake

 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214): error 
C2065: 'yyscan_t': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214): error 
C2146: syntax error: missing ';' before identifier 'scanner' 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(214): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215): error 
C2065: 'YY_BUFFER_STATE': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215): error 
C2146: syntax error: missing ';' before identifier 'in_buffer' 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(215): error 
C2065: 'in_buffer': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(235): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(243): error 
C2065: 'in_buffer': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(243): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(250): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(256): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(319): error 
C2065: 'in_buffer': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(319): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]
 C:\Development\ewireshark\trunk\epan\dfilter\dfilter.c(320): error 
C2065: 'scanner': undeclared identifier 
[C:\Development\wsbuild64\epan\dfilter\dfilter.vcxproj]


   "C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
   "C:\Development\wsbuild64\ALL_BUILD.vcxproj.metaproj" (default target) 
(2) ->
   "C:\Development\wsbuild64\ui\ui.vcxproj.metaproj" (default target) (113) 
->
   "C:\Development\wsbuild64\ui\ui.vcxproj" (default target) (165) ->
 C:\Development\ewireshark\trunk\ui\text_import.c(909): error C2065: 
'yyscan_t': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(909): error C2146: 
syntax error: missing ';' before identifier 'scanner' 
[C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(909): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1021): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1027): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1029): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]
 C:\Development\ewireshark\trunk\ui\text_import.c(1031): error C2065: 
'scanner': undeclared identifier [C:\Development\wsbuild64\ui\ui.vcxproj]

But dfilter is built with lemon isn't it? Flex is Cygwin 2.5.39-1 and there's 
not any newer version available...
Regards
Anders

-Original Message-
From: wireshark-dev-boun...@wireshark.org 
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Michal Labedzki
Sent: den 4 april 2016 12:37
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Current master not compiling

I have flex 2.5.35 and flex 2.6.0, but still not working for me.

On 4 April 2016 at 12:24, Guy Harris  wrote:
> On Apr 4, 2016, at 1:51 AM, Dario Lombardo  
> wrote:
>
>> But how did the buildbot let it pass?
>
> Because it has a newer version of Flex than you do?
>
> The current master-branch Wireshark, like the current master-branch libpcap, 
> requires at least Flex 2.5.31; Wireshark might require a newer version.  What 
> version do you have on your system?
>
> ___
> Sent via:Wireshark-dev mailing list

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Dario Lombardo 
On Mon, Apr 4, 2016 at 12:24 PM, Guy Harris  wrote:

> On Apr 4, 2016, at 1:51 AM, Dario Lombardo 
> wrote:
>
> > But how did the buildbot let it pass?
>
> Because it has a newer version of Flex than you do?
>
>
oh, yes... I didn't think about it :).


> The current master-branch Wireshark, like the current master-branch
> libpcap, requires at least Flex 2.5.31; Wireshark might require a newer
> version.  What version do you have on your system?
>
>
flex 2.5.39
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Michal Labedzki 
I have flex 2.5.35 and flex 2.6.0, but still not working for me.

On 4 April 2016 at 12:24, Guy Harris  wrote:
> On Apr 4, 2016, at 1:51 AM, Dario Lombardo  
> wrote:
>
>> But how did the buildbot let it pass?
>
> Because it has a newer version of Flex than you do?
>
> The current master-branch Wireshark, like the current master-branch libpcap, 
> requires at least Flex 2.5.31; Wireshark might require a newer version.  What 
> version do you have on your system?
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe



-- 

Pozdrawiam / Best regards
-
Michał Łabędzki, Software Engineer
Tieto Corporation

Product Development Services

http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wrocław, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorised use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to
the message and deleting it from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland spółka z ograniczoną odpowiedzialnością z siedzibą w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana w Sądzie Rejonowym
Szczecin-Centrum w Szczecinie, XIII Wydział Gospodarczy Krajowego
Rejestru Sądowego pod numerem 124858. NIP: 8542085557. REGON:
812023656. Kapitał zakładowy: 4 271500 PLN
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Guy Harris 
On Apr 4, 2016, at 1:51 AM, Dario Lombardo  wrote:

> But how did the buildbot let it pass?

Because it has a newer version of Flex than you do?

The current master-branch Wireshark, like the current master-branch libpcap, 
requires at least Flex 2.5.31; Wireshark might require a newer version.  What 
version do you have on your system?

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Current master not compiling

2016-04-04 Thread Michal Labedzki 
I have the same issue. See my comment:
https://code.wireshark.org/review/#/c/14719/

Moreover, if I define undefined type (text_import.c:909:5: error:
unknown type name ‘yyscan_t’) I get another issue:
dfilter.c:215:2: error: unknown type name ‘YY_BUFFER_STATE’

On 4 April 2016 at 10:51, Dario Lombardo  wrote:
> Today I'm not able to compile the current master
> 6f98a0fac33db70b3ceb71d939b0a9d0d47747cc.
>
> Using git bisect I've found that the culprit seems to be this commit
>
> commit 59816ef00c6dd09532d80b393ba03f8194aba236
> Author: Guy Harris 
> Date:   Wed Mar 30 18:44:01 2016 -0700
>
> Make the Flex scanners and YACC parser in libraries reentrant.
>
> But how did the buildbot let it pass? Anyone experiencing the same issue?
> Unfortunately I'm not goot with flex so I can't try to fix it myself.
> Bye
> Dario.
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe



-- 

Pozdrawiam / Best regards
-
Michał Łabędzki, Software Engineer
Tieto Corporation

Product Development Services

http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wrocław, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorised use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to
the message and deleting it from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland spółka z ograniczoną odpowiedzialnością z siedzibą w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana w Sądzie Rejonowym
Szczecin-Centrum w Szczecinie, XIII Wydział Gospodarczy Krajowego
Rejestru Sądowego pod numerem 124858. NIP: 8542085557. REGON:
812023656. Kapitał zakładowy: 4 271500 PLN
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Current master not compiling

2016-04-04 Thread Dario Lombardo 
Today I'm not able to compile the current
master 6f98a0fac33db70b3ceb71d939b0a9d0d47747cc.

Using git bisect I've found that the culprit seems to be this commit

commit 59816ef00c6dd09532d80b393ba03f8194aba236
Author: Guy Harris 
Date:   Wed Mar 30 18:44:01 2016 -0700

Make the Flex scanners and YACC parser in libraries reentrant.

But how did the buildbot let it pass? Anyone experiencing the same issue?
Unfortunately I'm not goot with flex so I can't try to fix it myself.
Bye
Dario.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] QT translation: lock keyboard shortcut terms?

2016-04-04 Thread Michal Labedzki 
Please note that some translations (not Wireshark only!) translate
arrow keys names (Up, Down, Left, Right).
For example: Polish. (I think it based on the fact that Enter,
Backspace, Shift, Ctrl, Alt, PrintScreen, Insert, Esc, etc. has
English name on the button, but arrows have only arrows (pictogram),
so it is better to translate them. So I am ok to lock all shortcut
without those with arrow and also if someone requests something... Let
me think... we should ask Russian, Chinese, etc. what they have on the
keyboard?

On 2 April 2016 at 00:24, Peter Wu  wrote:
> On Fri, Apr 01, 2016 at 08:27:57PM +0200, Uli Heilmeier wrote:
>> At the moment the translation source files ui/qt/wireshark_xx.ts contains
>> all the keyboard shortcuts (e.g. like 'Ctrl+Home'). Therefore these terms
>> are also listed in Transifex.
>>
>> However these terms are translated "automatically" with the qt_xx.qm
>> files. Doing a manually translation breaks the display of the shortcuts in
>> the UI (s.
>> https://www.wireshark.org/lists/wireshark-dev/201511/msg00101.html).
>>
>> I did the mistake to translate the terms some month ago and another
>> member of the German Transifex team has done the same mistake this week.
>>
>> How can we prevent this?
>> * Remove keyboard shortcuts from the wireshark_xx.ts file (if feasible)
>
> I looked through the manual
> (https://doc.qt.io/qt-5/linguist-translators.html) and did not find an
> option to disable translation for such options. It should however be
> possible to remove the shortcuts from the .ts files and add them to the
> cpp files instead using the setShortcut method of QActions. See:
>
>  - https://doc.qt.io/qt-5/qaction.html#shortcut-prop
>  - https://doc.qt.io/qt-5/qkeysequence.html#details
> --
> Kind regards,
> Peter Wu
> https://lekensteyn.nl
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe



-- 

Pozdrawiam / Best regards
-
Michał Łabędzki, Software Engineer
Tieto Corporation

Product Development Services

http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wrocław, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorised use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to
the message and deleting it from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland spółka z ograniczoną odpowiedzialnością z siedzibą w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana w Sądzie Rejonowym
Szczecin-Centrum w Szczecinie, XIII Wydział Gospodarczy Krajowego
Rejestru Sądowego pod numerem 124858. NIP: 8542085557. REGON:
812023656. Kapitał zakładowy: 4 271500 PLN
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe